Apparatus and methods for integrated high-capacity data and wireless network services

ABSTRACT

Apparatus and methods for unified high-bandwidth, low-latency data services provided with enhanced user mobility. In one embodiment, a network architecture having service delivery over at least portions of extant infrastructure (e.g., a hybrid fiber coax infrastructure) is disclosed, which includes standards-compliant ultra-low latency and high data rate services (e.g., 5G NR services) via a common service provider. In one variant, an expanded frequency band (e.g., 1.6 GHz in total bandwidth) is used over the coaxial portions of the HFC infrastructure, which is allocated to two or more sub-bands. Wideband amplifier apparatus are used to support delivery of the sub-bands to extant HFC network nodes (e.g., hubs or distribution points) within the network. Premises devices are used to provide the 5G-based services to users at a given premises and thereabouts. In another variant, local area (e.g., “pole mounted”) radio devices are used to provide supplemental RF coverage, including during mobility scenarios.

PRIORITY AND RELATED APPLICATIONS

This application claims the benefit of priority to U.S. ProvisionalPatent Application No. 62/658,465 filed Apr. 16, 2018 and entitled“APPARATUS AND METHODS FOR INTEGRATED HIGH-CAPACITY DATA AND WIRELESSNETWORK SERVICES”, which is incorporated herein by reference in itsentirety.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND 1. Technological Field

The present disclosure relates generally to the field of data networksand wireless devices, and specifically in one exemplary aspect to anarchitecture which integrates or unifies provision of high-speed dataservices in a variety of different locations and use cases.

2. Description of Related Technology

Data communication services are now ubiquitous throughout user premises(e.g., home, office, and even vehicles). Such data communicationservices may be provided via a managed or unmanaged network. Forinstance, a typical home has services provided by one or more networkservice providers via a managed network such as a cable or satellitenetwork. These services may include content delivery (e.g., lineartelevision, on-demand content, personal or cloud DVR, “start over”,etc.), as well as so-called “over the top” third party content.Similarly, Internet and telephony access is also typically provided, andmay be bundled with the aforementioned content delivery functions intosubscription packages, which are increasingly becoming more user- orpremises-specific in their construction and content. Such services arealso increasingly attempting to adopt the paradigm of “anywhere”,anytime,” so that users (subscribers) can access the desired services(e.g., watch a movie) via a number of different receiving and renderingplatforms, such as in different rooms of their house, on their mobiledevice while traveling, etc.

Managed Cable Networks

Network operators deliver data services (e.g., broadband) and videoproducts to customers using a variety of different devices, therebyenabling their users or subscribers to access data/content in a numberof different contexts, both fixed (e.g., at their residence) and mobile(such as while traveling or away from home). FIGS. 1 and 2 are afunctional block diagrams illustrating a typical prior art managed(e.g., cable) content delivery network architecture used to provide suchdata services to its users and subscribers.

Data/content delivery may be specific to the network operator, such aswhere video content is ingested by the network operator or its proxy,and delivered to the network users or subscribers as a product orservice of the network operator. For instance, a cable multiple systemsoperator (MSO) may ingest content from multiple different sources (e.g.,national networks, content aggregators, etc.), process the ingestedcontent, and deliver it to the MSO subscribers via e.g., a hybrid fibercoax (HFC) cable/fiber network, such as to the subscriber's set-top boxor DOC SIS cable modem. Such ingested content is transcoded to thenecessary format as required (e.g., MPEG-2 or MPEG-4/AVC), framed andplaced in the appropriate media container format (“packaged”), andtransmitted via e.g., statistical multiplex into a multi-programtransport stream (MPTS) on 6 MHz radio frequency (RF) channels forreceipt by the subscribers RF tuner, demultiplexed and decoded, andrendered on the user's rendering device (e.g., digital TV) according tothe prescribed coding format.

Within the cable plant, VOD and so-called switched digital video (SDV)may also be used to provide content, and utilize a single-programtransport stream (SPTS) delivery modality. In U. S. cable systems forexample, downstream RF channels used for transmission of televisionprograms are 6 MHz wide, and occupy a 6 MHz spectral slot between 54 MHzand 860 MHz. Deployments of VOD services have to share this spectrumwith already established analog and digital cable television servicessuch as those described above. Within a given cable plant, all homesthat are electrically connected to the same cable feed running through aneighborhood will receive the same downstream signal. For the purpose ofmanaging e.g., VOD services, these homes are grouped into logical groupstypically called Service Groups. Homes belonging to the same ServiceGroup receive their VOD service on the same set of RF channels.

VOD service is typically offered over a given number (e.g., 4) of RFchannels from the available spectrum in cable. Thus, a VOD Service Groupconsists of homes receiving VOD signals over the same 4 RF channels.

In most cable networks, programs are transmitted using MPEG (e.g.,MPEG-2) audio/video compression. Since cable signals are transmittedusing Quadrature Amplitude Modulation (QAM) scheme, available payloadbitrate for typical modulation rates (QAM-256) used on HFC systems isroughly 38 Mbps. For example, in many VOD deployments, a typical rate of3.75 Mbps is used to send one video program at resolution and qualityequivalent to NTSC broadcast signals. In digital television terminology,this is called Standard Definition (SD) television resolution.Therefore, use of MPEG-2 and QAM modulation enables carriage of 10 SDsessions on one RF channel (10×3.75=37.5 Mbps<38 Mbps). Since a typicalService Group consists of 4 RF channels, 40 simultaneous SD VOD sessionscan be accommodated within a Service Group.

Entertainment-quality transmission of HD (High Definition) signalsrequires about four times as much bandwidth as SD. For an exemplaryMPEG-2 Main Profile-High Level (MP@HL) video compression, each HDprogram requires around 15 Mbps bitrate.

OTT—

Alternatively, so-called “over-the-top” or OTT delivery may be used forproviding services within a network, wherein content from a third partysource who may be unaffiliated with the network operator providescontent directly to the requesting user or subscriber via the networkoperator's infrastructure (including the cable architecture describedsupra), e.g., via an IP-based transport; i.e., the content is packetizedand routed for delivery to the requesting user based on the user'snetwork or IP address, such as via the aforementioned high-speed DOCSIScable modem, according to the well-known Internet Protocol network-layerprotocol.

IP unicasts (point to point) or multicasts (point to multiple points)have traditionally been used as the mechanism by which the OTT contentis distributed over the network, via the user accessing a prescribed URLand logging in with their credentials to gain access to the content. TheIP content is then streamed via the unicast/multicast to the requestinguser(s), and received and decoded by a media player application program(“app”) on the user's PC, laptop, or other IP-enabled end-user device.

Cloud-Based Functions—

In order to gain operational and economic efficiencies, technologystacks within content delivery networks such as HFC-based cable networkshave over time generally migrated towards the “cloud” or network side ofthe network (e.g., into regionalized data centers), and away from theend user (client) consuming devices. Hence, the client device's contentpresentation capabilities are dictated increasingly by these cloud-basedfunctions (including network-side caching architecture), along with theon-board storage and processing power of the client device and itsassociated software stack.

For example, cloud-based EPGs (electronic program guides) areincreasingly configured to provide a streamlined user experience,reduced device processing and storage footprint, and a consistent andsimple mechanism for software upgrades across multiple different typesof HW/SW platforms (e.g., different OEM devices). For instance, HTML5-based cloud apps are increasingly replacing native apps (i.e., thoseincorporated into the design of the device at time of manufacture) forimplementing such functions. Implementations such as the cloud-based“Spectrum Guide” offered by the Assignee hereof is more labor intensivefor the client, due largely to the need for client processes orfunctions to interface with network-side entities or processes.

In the foregoing example of cloud-delivered EPGs, all objects (fromcontent poster art to the elements of the day/time grid, and most visualvideo content) is stitched and delivered as a single stream to theclient device (e.g., DSTB), as opposed to being indigenously generatedby the DSTB. Specifically, the program guide elements (e.g., graphics)are stitched together as a transport stream, while video content that isutilized within a window or other display element of this program guideon the user device comes from a different source, and any advertisementscome from yet a third location, akin to the operation of a web browser.This approach can present several challenges in performance,specifically with respect to latency associated with video transitionsfrom one program channel to another, from one type of content to another(such as VOD to DVR), as well as video content to advertising content(e.g., linear addressable content, described above) transitions. Even inthe most basic channel tuning functions, such transitions can takeseveral seconds, due to inter alia, the need to repopulate/generate EPGdisplay elements based on the cloud data and service.

As a brief aside, subscribers or users characteristically makeprogramming selection decisions in less than 1 second (based onanecdotal evidence of the Assignee hereof). Conversely, a typical userhas difficulty perceiving delays less than several milliseconds. Hence,the aforementioned multi-second latency or delay is highly detrimentalto user experience, including by failing to keep users engaged withparticular content, and with the service provider brand in general.

Other sources of delay in content switching transactions may exist aswell. For instance, where the (primary) video content is deliveredencoded in one format (e.g., H.264) and the switched-to content (e.g.,addressable advertisement) is encoded in a different format (e.g.,MPEG-2), delays in processing the MPEG-2 content may arise from, interalia, processing to support the rendering of MPEG-2 content (e.g.,identification and utilization of an MPEG-2 compatible decoder or playeron the client device). Conversely, the motion compensation and otherfeatures associated with H.264 and other advanced codecs (discussed ingreater detail below) can require significant processing overhead,thereby adding to the computational burden on the DSTB (or other clientdevice). Likewise, open-GOP (group of pictures) processing versusclosed-GOP processing can consume additional time and resources.

Wireless

A multitude of wireless networking technologies, also known as RadioAccess Technologies (“RATs”), provide the underlying means of connectionfor radio-based communication networks to user devices. Such RATs oftenutilize licensed radio frequency spectrum (i.e., that allocated by theFCC per the Table of Frequency Allocations as codified at Section 2.106of the Commission's Rules). Currently only frequency bands between 9 kHzand 275 GHz have been allocated (i.e., designated for use by one or moreterrestrial or space radio communication services or the radio astronomyservice under specified conditions). For example, a typical cellularservice provider might utilize spectrum for so-called “3G” (thirdgeneration) and “4G” (fourth generation) wireless communications asshown in Table 1 below:

TABLE 1 Technology Bands 3 G 850 MHz Cellular, Band 5 (GSM/GPRS/EDGE).1900 MHZ PCS, Band 2 (GSM/GPRS/EDGE). 850 MHz Cellular, Band 5(UMTS/HSPA + up to 21 Mbit/s). 1900 MHZ PCS, Band 2 (UMTS/HSPA + up to21 Mbit/s). 4 G 700 MHz Lower B/C, Band 12/17 (LTE). 850 MHz Cellular,Band 5 (LTE). 1700/2100 MHz AWS, Band 4 (LTE). 1900 MHz PCS, Band 2(LTE). 2300 MHz WCS, Band 30 (LTE).

Alternatively, unlicensed spectrum may be utilized, such as that withinthe so-called ISM-bands. The ISM bands are defined by the ITU RadioRegulations (Article 5) in footnotes 5.138, 5.150, and 5.280 of theRadio Regulations. In the United States, uses of the ISM bands aregoverned by Part 18 of the Federal Communications Commission (FCC)rules, while Part 15 contains the rules for unlicensed communicationdevices, even those that share ISM frequencies. Table 2 below showstypical ISM frequency allocations:

TABLE 2 Frequency Center range Type frequency Availability Licensedusers 6.765 MHz- A 6.78 MHz Subject to local Fixed service & mobile6.795 MHz acceptance service 13.553 MHz- B 13.56 MHz Worldwide Fixed &mobile services 13.567 MHz except aeronautical mobile (R) service 26.957MHz- B 27.12 MHz Worldwide Fixed & mobile service 27.283 MHz exceptaeronautical mobile service, CB radio 40.66 MHz- B 40.68 MHz WorldwideFixed, mobile services & 40.7 MHz earth exploration-satellite service433.05 MHz- A 433.92 MHz only in Region amateur service & 434.79 MHz 1,subject to radiolocation service, local acceptance additional apply theprovisions of footnote 5.280 902 MHz- B 915 MHz Region 2 only Fixed,mobile except 928 MHz (with some aeronautical mobile & exceptions)radiolocation service; in Region 2 additional amateur service 2.4 GHz- B2.45 GHz Worldwide Fixed, mobile, 2.5 GHz radiolocation, amateur &amateur-satellite service 5.725 GHZ- B 5.8 GHz WorldwideFixed-satellite, 5.875 GHz radiolocation, mobile, amateur &amateur-satellite service 24 GHz- B 24.125 GHz Worldwide Amateur,amateur-satellite, 24.25 GHz radiolocation & earth exploration-satelliteservice (active) 61 GHz- A 61.25 GHz Subject to local Fixed,inter-satellite, mobile 61.5 GHz acceptance & radiolocation service 122GHz- A 122.5 GHz Subject to local Earth exploration-satellite 123 GHzacceptance (passive), fixed, inter- satellite, mobile, space research(passive) & amateur service 244 GHz- A 245 GHz Subject to localRadiolocation, radio 246 GHz acceptance astronomy, amateur &amateur-satellite service

ISM bands are also been shared with (non-ISM) license-freecommunications applications such as wireless sensor networks in the 915MHz and 2.450 GHz bands, as well as wireless LANs (e.g., Wi-Fi) andcordless phones in the 915 MHz, 2.450 GHz, and 5.800 GHz bands.

Additionally, the 5 GHz band has been allocated for use by, e.g., WLANequipment, as shown in Table 3:

TABLE 3 Dynamic Freq. Selection Band Name Frequency Band Required (DFS)?UNII-1 5.15 to 5.25 GHz No UNII-2 5.25 to 5.35 GHz Yes UNII-2 Extended5.47 to 5.725 GHz Yes UNII-3 5.725 to 5.825 GHz No

User client devices (e.g., smartphone, tablet, phablet, laptop,smartwatch, or other wireless-enabled devices, mobile or otherwise)generally support multiple RATs that enable the devices to connect toone another, or to networks (e.g., the Internet, intranets, orextranets), often including RATs associated with both licensed andunlicensed spectrum. In particular, wireless access to other networks byclient devices is made possible by wireless technologies that utilizenetworked hardware, such as a wireless access point (“WAP” or “AP”),small cells, femtocells, or cellular towers, serviced by a backend orbackhaul portion of service provider network (e.g., a cable network). Auser may generally access the network at a node or “hotspot,” a physicallocation at which the user may obtain access by connecting to modems,routers, APs, etc. that are within wireless range.

One such technology that enables a user to engage in wirelesscommunication (e.g., via services provided through the cable networkoperator) is Wi-Fi® (IEEE Std. 802.11), which has become a ubiquitouslyaccepted standard for wireless networking in consumer electronics. Wi-Fiallows client devices to gain convenient high-speed access to networks(e.g., wireless local area networks (WLANs)) via one or more accesspoints.

Commercially, Wi-Fi is able to provide services to a group of userswithin a venue or premises such as within a trusted home or businessenvironment, or outside, e.g., cafes, hotels, business centers,restaurants, and other public areas. A typical Wi-Fi network setup mayinclude the user's client device in wireless communication with an AP(and/or a modem connected to the AP) that are in communication with thebackend, where the client device must be within a certain range thatallows the client device to detect the signal from the AP and conductcommunication with the AP.

Another wireless technology in widespread use is Long-Term Evolutionstandard (also colloquially referred to as “LTE,” “4G,” “LTE Advanced,”among others). An LTE network is powered by an Evolved Packet Core(“EPC”), an Internet Protocol (IP)-based network architecture andeNodeB—Evolved NodeB or E-UTRAN node which part of the Radio AccessNetwork (RAN), capable of providing high-speed wireless datacommunication services to many wireless-enabled devices of users with awide coverage area.

Currently, most consumer devices include multi-RAT capability; e.g.; thecapability to access multiple different RATs, whether simultaneously, orin a “fail over” manner (such as via a wireless connection managerprocess running on the device). For example, a smartphone may be enabledfor LTE data access, but when unavailable, utilize one or more Wi-Fitechnologies (e.g., 802.11g/n/ac) for data communications.

The capabilities of different RATs (such as LTE and Wi-Fi) can be verydifferent, including regarding establishment of wireless service to agiven client device. For example, there is a disparity between thesignal strength threshold for initializing a connection via Wi-Fi vs.LTE (including those technologies configured to operate in unlicensedbands such as LTE-U and LTE-LAA). As a brief aside, LTE-U enables datacommunication via LTE in an unlicensed spectrum (e.g., 5 GHz) to provideadditional radio spectrum for data transmission (e.g., to compensate foroverflow traffic). LTE-LAA uses carrier aggregation to combine LTE inunlicensed spectrum (e.g., 5 GHz) with the licensed band. Typical levelsof signal strength required for LTE-U or LTE-LAA service areapproximately −80 to −84 dBm. In comparison, Wi-Fi can be detected by aclient device based on a signal strength of approximately −72 to −80dBm, i.e., a higher (i.e., less sensitive) detection threshold.

Increasing numbers of users (whether users of wireless interfaces of theaforementioned standards, or others) invariably lead to “crowding” ofthe spectrum, including interference. Interference may also exist fromnon-user sources such as solar radiation, electrical equipment, militaryuses, etc. In effect, a given amount of spectrum has physicallimitations on the amount of bandwidth it can provide, and as more usersare added in parallel, each user potentially experiences moreinterference and degradation of performance.

Moreover, technologies such as Wi-Fi have limited range (due in part tothe unlicensed spectral power mask imposed in those bands), and maysuffer from spatial propagation variations (especially inside structuressuch as buildings) and deployment density issues. Wi-Fi has become soubiquitous that, especially in high-density scenarios such ashospitality units (e.g., hotels), enterprises, crowded venues, and thelike, the contention issues may be unmanageable, even with a plethora ofWi-Fi APs installed to compensate. Yet further, there is generally nocoordination between such APs, each in effect contending for bandwidthon its backhaul with others.

Additionally, lack of integration with other services provided by e.g.,a managed network operator, typically exists with unlicensed technologysuch as Wi-Fi. Wi-Fi typically acts as a “data pipe” opaquely carried bythe network operator/service provider.

5G New Radio (NR) and NG-RAN (Next Generation Radio Area Network)—

NG-RAN or “NextGen RAN (Radio Area Network)” is part of the 3GPP “5G”next generation radio system. 3GPP is currently specifying Release 15NG-RAN, its components, and interactions among the involved nodesincluding so-called “gNBs” (next generation Node B's or eNBs). NG-RANwill provide very high-bandwidth, very low-latency (e.g., on the orderof 1 ms or less “round trip”) wireless communication and efficientlyutilize, depending on application, both licensed and unlicensed spectrumof the type described supra in a wide variety of deployment scenarios,including indoor “spot” use, urban “macro” (large cell) coverage, ruralcoverage, use in vehicles, and “smart” grids and structures. NG-RAN willalso integrate with 4G/4.5G systems and infrastructure, and moreover newLTE entities are used (e.g., an “evolved” LTE eNB or “eLTE eNB” whichsupports connectivity to both the EPC (Evolved Packet Core) and the NR“NGC” (Next Generation Core).

In some aspects, exemplary Release 15 NG-RAN leverages technology andfunctions of extant LTE/LTE-A technologies (colloquially referred to as4G or 4.5G), as bases for further functional development andcapabilities. For instance, in an LTE-based network, upon startup, aneNB (base station) establishes S1-AP connections towards the MME(mobility management entity) whose commands the eNB is expected toexecute. An eNB can be responsible for multiple cells (in other words,multiple Tracking Area Codes corresponding to E-UTRAN Cell GlobalIdentifiers). The procedure used by the eNB to establish theaforementioned S1-AP connection, together with the activation of cellsthat the eNB supports, is referred to as the S1 SETUP procedure; seeinter alia, 3GPP TS 36.413 V14.4. entitled “3rd Generation PartnershipProject; Technical Specification Group Radio Access Network; EvolvedUniversal Terrestrial Radio Access Network (E-UTRAN); S1 ApplicationProtocol (S1AP) (Release 14)” dated September 2017, which isincorporated herein by reference in its entirety.

As a brief aside, and referring to FIG. 3 , the CU 304 (also known asgNB-CU) is a logical node within the NR architecture 300 thatcommunicates with the NG Core 303, and includes gNB functions such astransfer of user data, session management, mobility control, RANsharing, and positioning; however, other functions are allocatedexclusively to the DU(s) 306 (also known as gNB-DUs) per various “split”options described subsequently herein in greater detail. The CU 304communicates user data and controls the operation of the DU(s) 306, viacorresponding front-haul (Fs) user plane and control plane interfaces308, 310.

Accordingly, to implement the Fs interfaces 308, 310, the (standardized)F1 interface is employed. It provides a mechanism for interconnecting agNB-CU 304 and a gNB-DU 306 of a gNB 302 within an NG-RAN, or forinterconnecting a gNB-CU and a gNB-DU of an en-gNB within an E-UTRAN.The F1 Application Protocol (F1AP) supports the functions of F1interface by signaling procedures defined in 3GPP TS 38.473. F1APconsists of so-called “elementary procedures” (EPs). An EP is a unit ofinteraction between gNB-CU and gNB-DU. These EPs are defined separatelyand are intended to be used to build up complete messaging sequences ina flexible manner. Generally, unless otherwise stated by therestrictions, the EPs may be invoked independently of each other asstandalone procedures, which can be active in parallel.

Within such an architecture 300, a gNB-DU 306 (or ngeNB-DU) is under thecontrol of a single gNB-CU 304. When a gNB-DU is initiated (includingpower-up), it executes the F1 SETUP procedure (which is generallymodeled after the above-referenced S1 SETUP procedures of LTE) to informthe controlling gNB-CU of, inter alia, any number of parameters such ase.g., the number of cells (together with the identity of each particularcell) in the F1 SETUP REQUEST message.

Better Solutions Needed

Even with the great advances in wireless data rate, robustness andcoverage afforded by extant 4/4.5G (e.g. LTE/LTE-A) and WLAN (and otherunlicensed) systems, and corresponding IoT solutions outlined above,significant disabilities still exist.

One such problem relates to the scenario where a broadband user migratesfrom an indoor use case to an outdoor use case. For instance, a userutilizing their premises Wi-Fi AP experiences a very limitedrange—perhaps 100 feet or so depending on premises construction andother factors—before they experience degradation and ultimately loss ofsignal. Moreover, there is no session continuity between shorter rangetechnologies such as Wi-Fi and longer range broadband cellular systemssuch as LTE (i.e., a user must terminate their Wi-Fi session andcontinue using a new LTE (3GPP) session). Such “unlicensed to licensed”(and vice versa) spectral use also presents unique challenges, in thatunlicensed systems are often not configured to integrate with MNOsystems (e.g., WLAN APs are not configured to comply with 3GPP eUTRAN orother such standards as far as interoperability).

Moreover, the foregoing solutions are generally not integrated orlogically unified, and may also require subscription to and use ofmultiple service provider technologies and infrastructure. For example,unlicensed WLAN APs within a user premises may be backhauled by a cableor fiber or satellite MSO, while cellular service is provided by awholly separate MNO using licensed cellular infrastructure.

In cases where MNO or other radio access node or base stations arebackhauled by another provider (e.g., a wireless network built aroundHFC/DOCSIS as backhaul between the radio and wireless core networkelements), several disadvantages are encountered, including (i) separateCAPEX (capital expenditure) and OPEX (operating expenditure) “silos” formaintaining the two different networks; i.e., wired and wireless; and(ii) lower data throughput efficiency and higher latency due to theadditional overhead of encapsulating wireless data packets through e.g.,the DOCSIS (backhaul) protocols. In the context of the aforementionedultra-low latency requirements of 5G (i.e., 1 ms or less round-tripbetween endpoint nodes), such infrastructure-induced latency can resultin failing to meet these requirements, making this architecturepotentially unsuitable for 5G applications.

Moreover, to achieve certain capacity targets (e.g., 10 Gbps) over suchinfrastructure, increased use of optical fiber is needed in certainparts of the infrastructure. Under current HFC network design, servicesare provided to users via a coaxial cable “drop” to their premises, andgroups of such premises are served by common tap-off points or nodeswithin the larger architecture (see discussion of cable systems supra).Individual premises “tap off” the cabling or other infrastructure fromeach node and, depending on their geographic placement and otherconsiderations, may require utilization of a number of differentamplification units in order to maintain sufficient signal strength outto the most distant (topology-wise) premises in the system. Forinstance, a common description of how many amplifier stages are usedbetween a source node and premises is “N+i”, where i=the number ofamplifier stages between the source node and the premises. For instance,N=0 refers to the situation where no amplifiers are used, and N+3 refersto use of three (3) amplifiers. In some extant cable/HFC systems inoperation, values of i may be as high as seven (7); i.e., N+7, such asfor service to rural areas.

As can be expected, use of such amplifier stages introduces somelimitations on the data rates or bandwidth (both downstream; i.e.,toward the client premises, and upstream, i.e., from the clientpremises) achievable by such systems. In effect, such systems arelimited in maximum bandwidth/data rate, due in part to the design of theamplifiers; for example, they are typically designed to provide servicesprimarily in the downstream direction (with much lower upstreambandwidth via so-called “00B” or out-of band RF channels providinghighly limited upstream communication. Cable modem or DOCSIS-compliantsystems utilize DOCSIS QAMs (RF channels) for enhanced upstreambandwidth capability such as for Internet services, but even suchtechnologies are significantly limited in capability, and moreover havelimited flexibility in the allocation of downstream versus upstreambandwidth, especially dynamically.

Accordingly, as alluded to above, replacement of such amplifier stages(and supporting coaxial cabling) with higher bandwidth, low-loss mediumssuch as optical fiber is necessary to achieve very high target datarates (sometimes referred to as going “fiber deep”), including all theway back to an N+0 configuration throughout the entire network toachieve the highest data rates. However, replacement of literally tensof thousands of amplifiers and thousands of miles of cabling withoptical fiber or the like is prohibitively expensive, and can takeyears.

Accordingly, improved apparatus and methods are needed to, inter alia,enable optimized delivery of ultra-high data rate services (both wiredand wireless) and which leverage extant network infrastructure. Ideally,such improved apparatus and methods would also support seamlessgeographic and cross-platform mobility for users while providing suchservices, and support incipient applications and technologies such asIoT.

SUMMARY

The present disclosure addresses the foregoing needs by providing, interalia, methods and apparatus for providing optimized delivery ofultra-high data rate services (both wired and wireless) and whichleverage extant network infrastructure.

In a first aspect of the disclosure, a method of operating a radiofrequency (RF) network so that extant infrastructure is used to deliverintegrated wireless data services is disclosed. In one embodiment, themethod includes: transmitting OFDM (orthogonal frequency divisionmultiplexing) waveforms over at least a portion of the extantinfrastructure using at least a frequency band wider in frequency than anormal operating band of the extant infrastructure, the frequency bandbeing lower in frequency than a user frequency band; receiving thetransmitted OFDM waveforms via at least one premises device;upconverting the OFDM waveforms to the user frequency band to formupconverted waveforms; and transmitting the upconverted waveforms to atleast one user device.

In one variant, the extant infrastructure comprises a hybrid fiber coax(HFC) infrastructure, and the integrated wireless data services comprisedata delivery at rates in excess of 1 Gbps.

In one implementation, the frequency band wider in frequency than anormal operating band of the extant infrastructure comprises a frequencyband of at least 1.6 GHz in total bandwidth, and the further includingallocating the frequency band of at least 1.6 GHz in total bandwidth totwo or more sub-bands, such as via using wideband amplifier apparatus.

In another implementation, the allocating further comprises delivery ofthe two or more sub-bands to one or more extant HFC network hubs.

In another variant, the upconverting the OFDM waveforms to the userfrequency band comprises upconverting to a frequency band including 5GHz but excluding frequencies below 3 GHz.

In yet another variant, the transmitting the upconverted waveforms to atleast one user device comprises transmitting using at least a 3GPP FifthGeneration (5G) New Radio (NR) compliant air interface in an unlicensedradio frequency band.

In a further variant, the transmitting OFDM (orthogonal frequencydivision multiplexing) waveforms over at least a portion of the extantinfrastructure using at least a frequency band wider in frequency than anormal operating band of the extant infrastructure comprisestransmitting the OFDM waveforms over at least coaxial cable and via aplurality of amplifier stages associated with the coaxial cable.

In another aspect, a network architecture configured to support wirelessuser devices is disclosed. In one embodiment, the architecture includes:a distribution node, the distribution node configured to transmit radiofrequency (RF) waveforms onto a wireline or optical medium of a network,the RF waveforms being orthogonal frequency division multiplex (OFDM)modulated; and a first plurality of user nodes.

In one variant, each of the first plurality of user nodes is in datacommunication with the wireline or optical medium and includes areceiver apparatus configured to: receive the transmitted OFDM modulatedwaveforms; upconvert the OFDM modulated waveforms to at least one userfrequency band to form upconverted waveforms; and transmit theupconverted waveforms to at least one wireless user device.

In one implementation, the network architecture includes a radio node indata communication with the distribution node and at least one of thefirst plurality of user nodes, the radio node configured to provide atleast supplemental data communication to the at least one user node. Theradio node is in data communication with the distribution node via atleast an optical fiber medium, and the radio node is in datacommunication with the at least one user node via a wireless interface.

In another implementation, the radio node is in data communication withthe distribution node via at least an optical fiber medium, and theradio node is in data communication with the at least one user node viaa wireless interface.

In a further implementation, the network architecture includes a seconddistribution node, the second distribution node configured to transmitradio frequency (RF) waveforms onto a second wireline or optical mediumof the network, the RF waveforms being orthogonal frequency divisionmultiplex (OFDM) modulated, the second wireline or optical medium of thenetwork serving a second plurality of user nodes different than thefirst plurality of user nodes. The architecture may also include a radionode in data communication with at least the distribution node and (i)at least one of the first plurality of user nodes, and (ii) at least oneof the second plurality of user nodes, the radio node configured toprovide at least supplemental data communication to both the at leastone of the first plurality of user nodes, and the at least one of thesecond plurality of user nodes.

In one particular implementation, the radio node is in datacommunication with the distribution node via at least an optical fibermedium, and the radio node is in data communication with both the atleast one of the first plurality of user nodes, and the at least one ofthe second plurality of user nodes, via a wireless interface utilizingan unlicensed portion of the RF spectrum.

In another implementation, the network architecture includes at leastone wireless local area node, the at least one wireless local area nodein data communication with at least one of the first plurality of usernodes, the at least one wireless local area node configured towirelessly communicate with the at least one wireless user device viaunlicensed radio frequency spectrum not within the user frequency band.

The network architecture may also include at least one wireless localarea node controller in data communication with the distribution node,the at least one wireless local area node controller configured tocooperate with the distribution node to effect handover of one or morewireless sessions between the at least wireless local area node and theat least one of the first plurality of user nodes.

The at least one wireless local area node may operate for example withina first unlicensed frequency band, and the at least one of the firstplurality of user nodes operates within a second unlicensed frequencyband. For instance, the at least one wireless local area node mayoperate according to an IEEE-Std. 802.11 (Wi-Fi) protocol, and the atleast one of the first plurality of user nodes may operate according a3GPP 5G NR (Fifth Generation, New Radio) protocol.

In another aspect of the disclosure, a controller apparatus for usewithin a hybrid fiber/coaxial cable distribution network is described.In one embodiment, the controller apparatus includes: a radio frequency(RF) communications management module; a first data interface in datacommunication with the RF communications management module for datacommunication with a network core process; a second data interface indata communication with the RF communications management module for datacommunication with a first RF distribution node of the hybridfiber/coaxial cable distribution network; and a third data interface indata communication with the RF communications management module for datacommunication with a second RF distribution node of the hybridfiber/coaxial cable distribution network.

In one variant, the radio frequency (RF) communications managementmodule includes computerized logic to enable at least the transmissionof digital data from at least one of the first RF distribution node andthe second RF distribution node with an RF band outside of that normallyused by the at least one first RF distribution node and the second RFdistribution node.

In one implementation, the radio frequency (RF) communicationsmanagement module includes a 3GPP Fifth Generation New Radio (5G NR) gNB(gNodeB) Controller Unit (CU), the first data interface for datacommunication with a network core process includes a 3GPP FifthGeneration New Radio (5G NR) Xn interface with a 5GC (Fifth GenerationCore), and the second data interface includes a 3GPP Fifth GenerationNew Radio (5G NR) F1 interface operative over at least a wireline databearer medium, the first RF distribution node including a 3GPP FifthGeneration New Radio (5G NR) gNB (gNodeB) Distributed Unit (DU); and thethird data interface includes an Fifth Generation New Radio (5G NR) F1interface operative over at least a dense wave division multiplexed(DWDM) optical data bearer, the second RF distribution node including a3GPP Fifth Generation New Radio (5G NR) gNB (gNodeB) Distributed Unit(DU).

In one aspect, methods and apparatus for seamless mobility in a networkwith heterogeneous media using common control nodes is disclosed. In oneembodiment, the method includes use of common network elements and asplit CU-DU base-station architecture for providing a seamless mobilityexperience between indoor and outdoor spaces which are connected usingcommon waveforms and protocols through heterogeneous media, e.g., HFCand wireless. In one variant, the provided services include broadbanddata, mobility data, IoT and video streaming.

In another aspect, methods and apparatus for data throughputperformance-triggered mobility between 3GPP and Wi-Fi is provided. Inone embodiment, a centralized Wi-Fi controller is utilized; via datacommunication between the Wi-Fi controller and a 3GPP mobilitycontroller, both indoor and outdoor spaces are provided coordinated 3GPPand Wi-Fi service coverage.

In another aspect, an optical to coaxial cable transducer that cantransmit and receive 3GPP 4G LTE and 5G NR waveforms to multiple CPEthrough a single coaxial cable is disclosed.

In another aspect, methods and apparatus for supplementing broadbandcapacity available through a primary link is disclosed. In oneembodiment, the primary link includes a coaxial cable, and a redundantsupplemental link is provided. In one variant, one or more RF interfaceson a CPE are included for connecting the CPE to e.g., a 2-port externalantenna which is installed outdoors at the served premises. Thisexternal antenna can be used to receive supplemental signals fromoutdoor radios installed in the vicinity of the served premises. Theoutdoor radios may provide, inter alia, coverage for outdoor mobility,and/or in a “fixed-wireless” configuration to supplement the capacityfrom the primary coaxial link and/or to add redundancy.

In another aspect, computerized network apparatus for use in a datanetwork is disclosed. In one variant, the network includes an HFCnetwork with NG-RAN capability, and the apparatus includes at least oneenhanced DU (DUe).

In another variant, the network apparatus includes at least one enhancedCU (CUe), which can control a number of DU/DUe.

In yet another aspect, a system is disclosed. In one embodiment, thesystem includes (i) a controller entity, (ii) one or more distributedentities in data communication therewith via an HFC bearer. In onevariant, a further complementary or supplemental link is provided viae.g., wireless access nodes positioned external to a serviced premisesand which a premises CPE can access via a dedicated antenna apparatus.The access nodes are backhauled to a managed (HFC) network via extantcoaxial cable or fiber, or supplemental cable or fiber.

In still a further aspect of the disclosure, a method for providingdevice mobility is described. In one embodiment, the method includesproviding indoor wireless coverage via a wireless-enabled CPE backhauledby an HFC network, and providing outdoor wireless coverage via one ormore external (e.g., pole mounted) access nodes.

In another aspect of the disclosure, a method for providing devicemobility is described. In one embodiment, the method includes firstproviding indoor/outdoor premises wireless coverage via awireless-enabled CPE backhauled by an HFC network, and subsequentlyproviding outdoor wireless coverage via one or more external (e.g., polemounted) access nodes via a handover while maintaining data sessioncontinuity.

In a further aspect of the disclosure, a method for providing high speeddata services to a device is described. In one embodiment, the methodincludes providing indoor wireless coverage via a wireless-enabled CPEbackhauled by an HFC network, and supplementing that capability via oneor more external (e.g., pole mounted) access nodes that arecommunicative with the CPE via an external antenna apparatus. In onevariant, the external access nodes are backhauled by the same HFCnetwork.

In another aspect, a computerized access node implementing one or moreof the foregoing aspects is disclosed and described. In one embodiment,the access node includes a wireless interface capable of datacommunication with a user device (e.g., UE). In one variant, the deviceis pole-mounted (e.g., on a telephone or utility pole), and further isconfigured to interface with a premises CPE via e.g., an antennaapparatus mounted on an exterior of the premises.

In another aspect, a computerized premises device implementing one ormore of the foregoing aspects is disclosed and described. In oneembodiment, the device includes a CPE having 5G NR capability, and isbackhauled via an extant coaxial cable drop. In one variant, the devicealso includes a plurality of IoT wireless interfaces, and provision forconnection with an externally mounted antenna for use in communicatingwith one or more of the external access nodes.

In another aspect, a computerized device implementing one or more of theforegoing aspects is disclosed and described. In one embodiment, thedevice includes a personal or laptop computer. In another embodiment,the device includes a mobile device (e.g., tablet or smartphone). Inanother embodiment, the device includes a computerized “smart”television or rendering device.

In another aspect, an integrated circuit (IC) device implementing one ormore of the foregoing aspects is disclosed and described. In oneembodiment, the IC device is embodied as a SoC (system on Chip) device.In another embodiment, an ASIC (application specific IC) is used as thebasis of the device. In yet another embodiment, a chip set (i.e.,multiple ICs used in coordinated fashion) is disclosed. In yet anotherembodiment, the device includes a multi-logic block FPGA device.

In another aspect, a computer readable storage apparatus implementingone or more of the foregoing aspects is disclosed and described. In oneembodiment, the computer readable apparatus includes a program memory,or an EEPROM. In another embodiment, the apparatus includes a solidstate drive (SSD) or other mass storage device. In another embodiment,the apparatus includes a USB or other “flash drive” or other suchportable removable storage device. In yet another embodiment, theapparatus includes a “cloud” (network) based storage device which isremote from yet accessible via a computerized user or client electronicdevice. In yet another embodiment, the apparatus includes a “fog”(network) based storage device which is distributed across multiplenodes of varying proximity and accessible via a computerized user orclient electronic device.

In a further aspect, an optical-to-coaxial cable transducer that cantransmit and receive 3GPP 4G LTE and 5G NR waveforms to multiple CPEthrough a single coaxial cable interface is disclosed.

In a further aspect, a method of introducing expanded data networkservices within a network infrastructure are disclosed. In oneembodiment, the network includes an HFC cable network, and the methodincludes (i) utilizing extant bearer media (e.g., coaxial cable topremises) as a primary backhaul for high speed data services, and (ii)subsequently using extant bearer media (e.g., coaxial cable or opticalfiber to extant wireless nodes such as cellular base stations) toprovide supplemental bandwidth/mobility services to the premises users.In another variant, the method further includes (iii) subsequentlyinstalling new optical fiber or other media to support backhaul of new(currently non-existent “pole mounted” or similar opportunistic accessnodes which support further user mobility for the users/subscribers ofthe network operator.

These and other aspects shall become apparent when considered in lightof the disclosure provided herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1 and 2 are a functional block diagrams illustrating a typicalprior art managed (e.g., cable) content delivery network architecture.

FIG. 3 is a functional block diagram of a prior art gNB architectureincluding CU and multiple DUs.

FIG. 4 a is a graphical representation of frequency bands associatedwith prior art IEEE Std. 802.15.4 and Bluetooth Low Energy (BLE)wireless interfaces.

FIG. 4 b is a graphical representation of frequency bands associatedwith prior art IEEE Std. 802.15.4 and Wi-Fi wireless interfaces.

FIG. 5 is a functional block diagram of an exemplary MSO networkarchitecture comprising various features described herein.

FIG. 5 a is a functional block diagram of one exemplary embodiment of agNB architecture including CUe and multiple DUes, according to thepresent disclosure.

FIG. 5 b is a functional block diagram of another exemplary embodimentof a gNB architecture including multiple CUes and multiple correspondingDUes, according to the present disclosure.

FIG. 5 c is a functional block diagram of yet another exemplaryembodiment of a gNB architecture including multiple CUes logicallycross-connected to multiple different cores, according to the presentdisclosure.

FIGS. 6 a and 6 b illustrate exemplary downstream (DS) and upstream (US)data throughputs or rates as a function of distance within the HFC cableplant of FIG. 5 .

FIG. 7 is a functional block diagram illustrating an exemplary generalconfiguration of a network node apparatus according to the presentdisclosure.

FIG. 7 a is a functional block diagram illustrating an exemplaryimplementation of the network node apparatus according to the presentdisclosure, configured for 3GPP 4G and 5G capability.

FIG. 8 is a functional block diagram illustrating an exemplary generalconfiguration of a CPEe apparatus according to the present disclosure.

FIG. 8 a is a functional block diagram illustrating an exemplaryimplementation of a CPEe apparatus according to the present disclosure,configured for 3GPP 4G and 5G capability.

FIG. 9 a is a block diagram illustrating an exemplary embodiment of asupplemental wireless link architecture supporting indoor enhancedbandwidth capability, according to the present disclosure.

FIG. 9 b is a block diagram illustrating an exemplary embodiment of asupplemental wireless link architecture supporting indoor/outdoormobility transitions, according to the present disclosure.

FIG. 10 is a block diagram illustrating an exemplary embodiment of awireless link architecture supporting outdoor mobility via combined cellcoverage, according to the present disclosure.

FIG. 11 is a block diagram illustrating one embodiment of anarchitecture for providing high data rate, low latency and high mobilityunified coverage to e.g., large indoor spaces such as office buildings,enterprises, universities, etc.

FIG. 12 is a logical flow diagram illustrating one embodiment of ageneralized method of utilizing an existing network (e.g., HFC) forhigh-bandwidth data communication.

FIG. 12 a is a logical flow diagram illustrating one particularimplementation of content processing and transmission according to thegeneralized method of FIG. 12 .

FIG. 12 b is a logical flow diagram illustrating one particularimplementation of content reception and digital processing by a CPEeaccording to the generalized method of FIG. 12 .

FIG. 12 c is a logical flow diagram illustrating one particularimplementation of content reception and transmission within a premisesby a CPEe according to the generalized method of FIG. 12 .

All figures © Copyright 2017-2018 Charter Communications Operating, LLC.All rights reserved.

DETAILED DESCRIPTION

Reference is now made to the drawings wherein like numerals refer tolike parts throughout.

As used herein, the term “application” (or “app”) refers generally andwithout limitation to a unit of executable software that implements acertain functionality or theme. The themes of applications vary broadlyacross any number of disciplines and functions (such as on-demandcontent management, e-commerce transactions, brokerage transactions,home entertainment, calculator etc.), and one application may have morethan one theme. The unit of executable software generally runs in apredetermined environment; for example, the unit could include adownloadable Java Xlet™ that runs within the JavaTV™ environment.

As used herein, the term “central unit” or “CU” refers withoutlimitation to a centralized logical node within a wireless networkinfrastructure. For example, a CU might be embodied as a 5G/NR gNBCentral Unit (gNB-CU), which is a logical node hosting RRC, SDAP andPDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB thatcontrols the operation of one or more gNB-DUs, and which terminates theF1 interface connected with one or more DUs (e.g., gNB-DUs) definedbelow.

As used herein, the terms “client device” or “user device” or “UE”include, but are not limited to, set-top boxes (e.g., DSTBs), gateways,modems, personal computers (PCs), and minicomputers, whether desktop,laptop, or otherwise, and mobile devices such as handheld computers,PDAs, personal media devices (PMDs), tablets, “phablets”, smartphones,and vehicle infotainment systems or portions thereof.

As used herein, the term “computer program” or “software” is meant toinclude any sequence or human or machine cognizable steps which performa function. Such program may be rendered in virtually any programminglanguage or environment including, for example, C/C++, Fortran, COBOL,PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML,VoXML), and the like, as well as object-oriented environments such asthe Common Object Request Broker Architecture (CORBA), Java™ (includingJ2ME, Java Beans, etc.) and the like.

As used herein, the term “distributed unit” or “DU” refers withoutlimitation to a distributed logical node within a wireless networkinfrastructure. For example, a DU might be embodied as a 5G/NR gNBDistributed Unit (gNB-DU), which is a logical node hosting RLC, MAC andPHY layers of the gNB or en-gNB, and its operation is partly controlledby gNB-CU (referenced above). One gNB-DU supports one or multiple cells,yet a given cell is supported by only one gNB-DU. The gNB-DU terminatesthe F1 interface connected with the gNB-CU.

As used herein, the term “DOCSIS” refers to any of the existing orplanned variants of the Data Over Cable Services InterfaceSpecification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0and 3.1.

As used herein, the term “headend” or “backend” refers generally to anetworked system controlled by an operator (e.g., an MSO) thatdistributes programming to MSO clientele using client devices, orprovides other services such as high-speed data delivery and backhaul.

As used herein, the terms “Internet” and “internet” are usedinterchangeably to refer to inter-networks including, withoutlimitation, the Internet. Other common examples include but are notlimited to: a network of external servers, “cloud” entities (such asmemory or storage not local to a device, storage generally accessible atany time via a network connection, and the like), service nodes, accesspoints, controller devices, client devices, etc.

As used herein, the term “IoT device” refers without limitation toelectronic devices having one or more primary functions and beingconfigured to provide and/or receive data via one or more communicationprotocols. Examples of IoT devices include security or monitoringsystems, appliances, consumer electronics, vehicles, infrastructure(e.g., traffic signaling systems), and medical devices, as well asreceivers, hubs, proxy devices, or gateways used in associationtherewith.

As used herein, the term “IoT network” refers without limitation to anylogical, physical, or topological connection or aggregation of two ormore IoT devices (or one IoT device and one or more non-IoT devices).Examples of IoT networks include networks of one or more IoT devicesarranged in a peer-to-peer (P2P), star, ring, tree, mesh, master-slave,and coordinator-device topology.

As used herein, the term “LTE” refers to, without limitation and asapplicable, any of the variants or Releases of the Long-Term Evolutionwireless communication standard, including LTE-U (Long Term Evolution inunlicensed spectrum), LTE-LAA (Long Term Evolution, Licensed AssistedAccess), LTE-A (LTE Advanced), 4G LTE, WiMAX, VoLTE (Voice over LTE),and other wireless data standards.

As used herein, the term “memory” includes any type of integratedcircuit or other storage device adapted for storing digital dataincluding, without limitation, ROM, PROM, EEPROM, DRAM, SDRAM, DDR/2SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), 3Dmemory, and PSRAM.

As used herein, the terms “microprocessor” and “processor” or “digitalprocessor” are meant generally to include all types of digitalprocessing devices including, without limitation, digital signalprocessors (DSPs), reduced instruction set computers (RISC),general-purpose (CISC) processors, microprocessors, gate arrays (e.g.,FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors,secure microprocessors, and application-specific integrated circuits(ASICs). Such digital processors may be contained on a single unitary ICdie, or distributed across multiple components.

As used herein, the terms “MSO” or “multiple systems operator” refer toa cable, satellite, or terrestrial network provider havinginfrastructure required to deliver services including programming anddata over those mediums.

As used herein, the terms “MNO” or “mobile network operator” refer to acellular, satellite phone, WMAN (e.g., 802.16), or other network serviceprovider having infrastructure required to deliver services includingwithout limitation voice and data over those mediums. The term “MNO” asused herein is further intended to include MVNOs, MNVAs, and MVNEs.

As used herein, the terms “network” and “bearer network” refer generallyto any type of telecommunications or data network including, withoutlimitation, hybrid fiber coax (HFC) networks, satellite networks, telconetworks, and data networks (including MANs, WANs, LANs, WLANs,internets, and intranets). Such networks or portions thereof may utilizeany one or more different topologies (e.g., ring, bus, star, loop,etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeterwave, optical, etc.) and/or communications technologies or networkingprotocols (e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay,3GPP, 3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, 5GNR, WAP, SIP, UDP, FTP,RTP/RTCP, H.323, etc.).

As used herein the terms “5G” and “New Radio (NR)” refer withoutlimitation to apparatus, methods or systems compliant with 3GPP Release15, and any modifications, subsequent Releases, or amendments orsupplements thereto which are directed to New Radio technology, whetherlicensed or unlicensed.

As used herein, the term “QAM” refers to modulation schemes used forsending signals over e.g., cable or other networks. Such modulationscheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM,256-QAM, etc.) depending on details of a network. A QAM may also referto a physical channel modulated according to the schemes.

As used herein, the term “server” refers to any computerized component,system or entity regardless of form which is adapted to provide data,files, applications, content, or other services to one or more otherdevices or entities on a computer network.

As used herein, the term “storage” refers to without limitation computerhard drives, DVR device, memory, RAID devices or arrays, optical media(e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices ormedia capable of storing content or other information.

As used herein, the term “Wi-Fi” refers to, without limitation and asapplicable, any of the variants of IEEE Std. 802.11 or related standardsincluding 802.11 a/b/g/n/s/v/ac/ax, 802.11-2012/2013 or 802.11-2016, aswell as Wi-Fi Direct (including inter alia, the “Wi-Fi Peer-to-Peer(P2P) Specification”, incorporated herein by reference in its entirety).

Overview

In one exemplary aspect, the present disclosure provides improvedarchitectures, methods and apparatus for providing enhanced ultra-highdata rate services which, inter alia, leverage existing managed network(e.g., cable network) infrastructure. The disclosed architectures enablea highly uniform user-experience regardless of the environment (e.g.,indoor/outdoor/mobility), in which content is consumed and eliminatesthe need to distinguish between fixed-broadband and mobile-broadband, orthe foregoing and IoT.

In one embodiment, a Hybrid Fiber Coax (HFC) plant infrastructure andextant 3GPP LTE and 5G NR protocols are used as bases for provision ofstandards-compliant ultra-low latency and high data rate services (e.g.,5G NR services) via a common service provider. In one variant, anexpanded frequency band (approximately 1.6 GHz in total bandwidth) isused over the coaxial portions of the HFC infrastructure, which isallocated to two or more sub-bands. Wideband amplifier apparatus areused to support delivery of the sub-bands to extant HFC network nodes(e.g., hubs or distribution points) within the network, and ultimatelyto premises devices. An OFDM and TDD-based access and modulation schemeis used to allow for maximal efficiency and flexibility in allocatingbandwidth to UL and DL transmissions over the HFC infrastructure.

5G-enabled premises devices (e.g., CPE) are used within the foregoingarchitecture to provide the services to users at a given premises andthereabouts, using extant 3GPP protocols. In another variant, local area(e.g., “pole mounted”) radio access nodes are used in concert with the5G-enabled CPE to provide supplemental RF coverage, including duringmobility scenarios, as well as supplemental capacity to the CPE forindoor use cases (i.e., when the CPE requires additional bandwidth overwhat the HFC coaxial cable drop to the premises alone can provide),thereby enabling data rates on the order of 10 Gbps and above.

Advantageously, in exemplary embodiments, the foregoing enhanced highdata rate, high mobility, low latency services are provided without (i)the need for any module or customized application software or protocolsof the user device (e.g., mobile UE), and (ii) the need to expendCAPEX/OPEX relating to laying new fiber and/or maintaining two (e.g.,MSO and MNO) network infrastructures in parallel.

Moreover, latency within the disclosed infrastructure is reduced by,inter alia, obviating encapsulation and other network/transportprotocols normally necessitated through use of e.g., DOCSIS bearers andequipment (i.e., DOCSIS modems and CMTS apparatus within the MSO core.

Edge-heavy solutions (e.g., Fog models) are also supported via the useof the 5G protocols as well as high bandwidth and enhanced connectivityout at the edge of the MSO infrastructure.

Using 3GPP protocols through HFC also enables broadband service benefitsstemming from the rich feature set, vendor diversity and operationalreliability that 3GPP has already developed for the over 2.6 billionglobal subscribers of 3GPP 4G LTE.

The improved architecture also advantageously facilitates so-called“network slicing,” including providing differentiated services (andQoS/QoE) for various target applications and use cases.

Detailed Description of Exemplary Embodiments

Exemplary embodiments of the apparatus and methods of the presentdisclosure are now described in detail. While these exemplaryembodiments are described in the context of the previously mentionedwireless access nodes (e.g., gNBs) associated with or supported at leastin part by a managed network of a service provider (e.g., MSO), othertypes of radio access technologies (“RATs”), other types of networks andarchitectures that are configured to deliver digital data (e.g., text,images, games, software applications, video and/or audio) may be usedconsistent with the present disclosure. Such other networks orarchitectures may be broadband, narrowband, or otherwise, the followingtherefore being merely exemplary in nature.

It will also be appreciated that while described generally in thecontext of a network providing service to a customer or consumer or enduser or subscriber (i.e., within a prescribed service area, venue, orother type of premises), the present disclosure may be readily adaptedto other types of environments including, e.g., commercial/retail, orenterprise domain (e.g., businesses), or even governmental uses. Yetother applications are possible.

Other features and advantages of the present disclosure will immediatelybe recognized by persons of ordinary skill in the art with reference tothe attached drawings and detailed description of exemplary embodimentsas given below.

Service Provider Network Architecture—

Referring now to FIG. 5 , one embodiment of an enhanced service providernetwork architecture 500 is shown and described in detail.

As illustrated, the architecture 500 includes one or more hubs 505within the MSO network (e.g., whether near edge portions of the network,or further towards the core), including a 5G NR core (5GC) 503. The hub505 includes a WLAN controller process 515, and services one or more“enhanced” nodes 501, which each include a gNB CUe 504 and an networkradio node 509, described in greater detail below. The nodes 501 utilizeHFC infrastructure, including N-way taps 512 to deliver RF waveforms tothe various served premises (including the enhanced CPE or CPEe) 513.

Also serviced by the node 501 are one or more non-CUe enabled nodes 511including 4G/5G enabled network radio nodes 509, which serviceadditional premises as shown.

In the illustrated embodiment, the nodes 501, 511 are backhauled byoptical fiber, although this is merely illustrative, as other types ofbackhauls including e.g., high-bandwidth wireless may be used consistentwith the present disclosure.

Similarly, one or more pole-mounted radio nodes 506 a are backhauled tothe MSO network via optical fiber (or other medium); these nodes 506 aprovide, inter alia, supplemental capacity/coverage for both indoor andoutdoor (and mobility) scenarios as described in greater detail below.

A Wi-Fi router device 517 is also present in the served premises toprovide WLAN coverage, in conjunction with the controller 515 at the hub505. The centralized Wi-Fi controller 515 is also utilized in theexemplary architecture 500 for tight-interworking and better mobilitybetween the 3GPP and Wi-Fi access technologies where the Wi-Fi router iseither integrated with the consumer premises equipment (e.g., enhancedCPE or CPEe) or connected to it. Then, mobility between the 3GPP andWi-Fi channels for any user can be triggered for the best datathroughput, such as based on (i) estimation of the RF quality of theWi-Fi channel toward the user, and/or (ii) the degree of congestion ofthe Wi-Fi router, and not just the Wi-Fi received signal strengthindicators (RSSI) measured at the mobile device, the latter which maynot be representative of the service quality that can be obtained by theuser.

In the exemplary configuration, the controller (e.g., Wi-Fi Controller515) is configured to choose the best (optimal) wireless connectionavailable to it based on performance (as opposed to coverage/coveragearea alone). Typically today, a preferred method of access ispredetermined based on its received signal strength and/or as apreferred means (e.g. Wi-Fi could be defined as the preferred method ofaccess to offload the mobile wireless network). However, this methodsuffers from the drawback of blind ‘stickiness’ to a technology, withoutconsidering the end user experience. Given that in exemplary embodimentsof the architecture described herein, both Wi-Fi and licensed/unlicensed3GPP access technologies are both controlled by the network operator(e.g. MSO), there is no need to prefer an access method, such as topurely to offload a user's traffic. The decision to offload or steer auser to a given access technology, can be based upon other criteria,such as e.g., a select set of Key Performance Indicators (KPIs) such asthe user perceived latency, throughput, packet loss, jitter andbit/packet/frame error rates as measured in real-time at any given layer(e.g., L1, L2 or L3) by the network. For instance, in oneimplementation, once a target KPI threshold is triggered, the switchingof the user can be triggered by either the AMF function (for 3GPP) orWi-Fi Controller. This switching may then trigger a sessionestablishment at the alternate access medium to transfer the user tothat technology. This helps optimize QoE for connected users, since thecontroller will always be attempting to holistically optimize theconnection versus merely making decisions based on coverage or signalstrength alone.

This architecture also obviates the problematic transition betweenpremises Wi-Fi and cellular, thereby enabling content consumption whilethe user is mobile, with no reduction in QoE or interruptions due toe.g., new session establishment in the cellular network. This isaccomplished by, inter alia, communication between the Wi-Fi controller515 and the CUe 504, such that the CUe can remain cognizant of bothWi-Fi and 3GPP channel status, performance and availability.Advantageously, in exemplary embodiments, the foregoing enhancedmobility is provided without the need for any module or customizedapplication software or protocols of the user device (e.g., mobile UE),since all communication sessions (whether between the CPEe and the UE,or the supplemental radio access node and the UE) are both (i)controlled by a common system, and (ii) utilize extant 3GPP (e.g.,4G/4.5G/5G) protocols and architectural elements. In one variant a GPRSTunneling Protocol (GTP) is utilized for maintenance of sessioncontinuity between the heterogeneous RAN technologies (e.g., 3GPP andIEEE Std. 802.11). In another variant, a PMIP (Proxy Mobile IP) basedapproach is utilized for session maintenance/handover. In yet a furthervariant, techniques described in 3GPP TS 23.234 v13.1.0, “3GPP system toWireless Local Area Network (WLAN) interworking; System description(Release 13),” incorporated herein by reference in its entirety, (aka“I-WLAN”) based approach is utilized for these purposes. As will beappreciated by those of ordinary skill given the present disclosure,combinations of the foregoing mechanisms may be utilized as well,depending on the particular application (including the two heterogeneoustechnologies that are party to the session maintenance/handoff).

The MSO network architecture 500 of FIG. 5 is particularly useful forthe delivery of packetized content (e.g., encoded digital contentcarried within a packet or frame structure or protocol) consistent withthe various aspects of the present disclosure. In addition to on-demandand broadcast content (e.g., live video programming), the system of FIG.5 may deliver Internet data and OTT (over-the-top) services to the endusers (including those of the DUe's 506) via the Internet protocol (IP)and TCP (i.e., over the 5G radio bearer), although other protocols andtransport mechanisms of the type well known in the digital communicationart may be substituted.

The architecture 500 of FIG. 5 further provides a consistent andseamless user experience with IPTV over both wireline and wirelessinterfaces. Additionally, in the IP paradigm, dynamic switching betweenunicast delivery and multicast/broadcast is used based on e.g., localdemand. For instance, where a single user (device) is requestingcontent, an IP unicast can be utilized. For multiple devices (i.e., withmultiple different IP addresses, such as e.g., different premises),multicast can be utilized. This approach provides for efficient andresponsive switching of delivery and obviates other moreequipment/CAPEX-intensive approaches.

Moreover, the architecture can be used for both broadband data deliveryas well as “content” (e.g., movie channels) simultaneously, and obviatesmuch of the prior separate infrastructure for “in band” and DOCSIS (andOOB) transport. Specifically, with DOCSIS (even FDX DOCSIS), bandwidthis often allocated for video QAMs, and a “split” is hard-coded fordownstream and upstream data traffic. This hard split is typicallyimplemented across all network elements—even amplifiers. In contrast,under the exemplary configuration of the architecture disclosed herein,effectively all traffic traversing the architecture is IP-based, andhence in many cases there is no need to allocate QAMs and frequencysplits for different program or data streams. This “all-IP” approachenables flexible use of the available bandwidth on the transmissionmedium for all applications dynamically, based on for instance thedemand of each such application at any given period or point in time.

In certain embodiments, the service provider network 500 alsoadvantageously permits the aggregation and/or analysis of subscriber- oraccount-specific data (including inter alia, correlation of particularCUe or DUe or E-UTRAN eNB/femtocell devices associated with suchsubscriber or accounts) as part of the provision of services to usersunder the exemplary delivery models described herein. As but oneexample, device-specific IDs (e.g., gNB ID, Global gNB Identifier, NCGI,MAC address or the like) can be cross-correlated to MSO subscriber datamaintained at e.g., the network head end(s) 507 so as to permit or atleast facilitate, among other things, (i) user/device authentication tothe MSO network; (ii) correlation of aspects of the area, premises orvenue where service is provided to particular subscriber capabilities,demographics, or equipment locations, such as for delivery oflocation-specific or targeted content or advertising or 5G “slicing”configuration or delivery; and (iii) determination of subscriptionlevel, and hence subscriber privileges and access to certain services asapplicable.

Moreover, device profiles for particular devices (e.g., 3GPP 5g NR andWLAN-enabled UE, or the CPEe 513 and any associated antenna 516, etc.)can be maintained by the MSO, such that the MSO (or its automated proxyprocesses) can model the device for wireless or other capabilities. Forinstance, one (non-supplemented) CPEe 513 may be modeled as havingbandwidth capability of X Gbps, while another premises' supplementedCPEe may be modeled as having bandwidth capability of X+Y Gbps, andhence the latter may be eligible for services or “slices” that are notavailable to the former.

As a brief aside, the 5G technology defines a number of networkfunctions (NFs), which include the following:

1. Access and Mobility Management function (AMF)—Provides fortermination of NAS signaling, NAS integrity protection and ciphering,registration and connection and mobility management, accessauthentication and authorization, and security context management. TheAMF has functions analogous to part of the MME functionality of theprior Evolved Packet Core (EPC).

2. Application Function (AF)—Manages application influence on trafficrouting, accessing NEF, interaction with policy framework for policycontrol. The NR AF is comparable to the AF in EPC.

3. Authentication Server Function (AUSF)—Provides authentication serverfunctionality. The AUSF is similar to portions of the HSS from EPC.

4. Network Exposure function (NEF)—Manages exposure of capabilities andevents, secure provision of information from external applications to3GPP network, translation of internal/external information. The NEF is awholly new entity as compared to EPC.

5. Network Slice Selection Function (NSSF)—Provides for selection of theNetwork Slice instances to serve the UE, determining the allowed NSSAI,determining the AMF set to be used to serve the UE. The NSSF is a whollynew entity as compared to EPC.

6. NF Repository function (NRF)—Supports the service discovery function,maintains NF profile and available NF instances The NRF is a wholly newentity as compared to EPC.

7. Policy Control Function (PCF)—Provides a unified policy framework,providing policy rules to CP functions, and access subscriptioninformation for policy decisions in UDR. The PCF has part of the PCRFfunctionality from EPC.

8. Session Management function (SMF)—Provides for session management(session establishment, modification, release), IP address allocation &management for UEs, DHCP functions, termination of NAS signaling relatedto session management, DL data notification, traffic steeringconfiguration for UPF for proper traffic routing. The SMF includesportions of the MME and PGW functionality from EPC.

9. Unified Data Management (UDM)—Supports generation of Authenticationand Key Agreement (AKA) credentials, user identification handling,access authorization, subscription management. This comprises a portionof HSS functionality from EPC.

10. User plane function (UPF)—The UPF provides packet routing &forwarding, packet inspection, QoS handling, and also acts as anexternal PDU session point of interconnect to Data Network (DN). The UPFmay also act as an anchor point for intra-RAT and inter-RAT mobility.The UPF includes some of the prior SGW and PGW functionality from EPC.

Within the 5G NR architecture, the control plane (CP) and user plane(UP) functionality is divided within the core network or NGC (NextGeneration Core). For instance, the 5G UPF discussed above supports UPdata processing, while other nodes support CP functions. This dividedapproach advantageously allows for, inter alia, independent scaling ofCP and UP functions. Additionally, network slices can be tailored tosupport different services, such as for instance those described hereinwith respect to session handover between e.g., WLAN and 3GPP NR, andsupplemental links to the CPEe.

In addition to the NFs described above, a number of differentidentifiers are used in the NG-RAN architecture, including those of UE'sand for other network entities, and may be assigned to various entitiesdescribed herein. Specifically:

-   -   the AMF Identifier (AMF ID) is used to identify an AMF (Access        and Mobility Management Function);    -   the NR Cell Global Identifier (NCGI), is used to identify NR        cells globally, and is constructed from the PLMN identity to        which the cell belongs, and the NR Cell Identity (NCI) of the        cell;    -   the gNB Identifier (gNB ID) is used to identify gNBs within a        PLMN, and is contained within the NCI of its cells;    -   the Global gNB ID, which is used to identify gNBs globally, and        is constructed from the PLMN identity to which the gNB belongs,        and the gNB ID;    -   the Tracking Area identity (TAI), which is used to identify        tracking areas, and is constructed from the PLMN identity to        which the tracking area belongs, and the TAC (Tracking Area        Code) of the Tracking Area; and    -   the Single Network Slice Selection Assistance information        (S-NSSAI), which is used to identify a network slice.        Hence, depending on what data is useful to the MSO or its        customers, various portions of the foregoing can be associated        and stored to particular gNB “clients” or their components being        backhauled by the MSO network.

Distributed gNB Architectures

In the context of FIG. 5 , the DUe's described herein may assume anynumber of forms and functions relative to the enhanced CPE (CPEe) 513and the radio node 506 a (e.g., pole mounted external device).Recognizing that generally speaking, “DU” and “CU” refer to 3GPPstandardized features and functions, these features and functions can,so long as supported in the architecture 500 of FIG. 5 , be implementedin any myriad number of ways and/or locations. Moreover, enhancementsand/or extensions to these components (herein referred to as CUe andDUe) and their functions provided by the present disclosure may likewisebe distributed at various nodes and locations throughout thearchitecture 500, the illustrated locations and dispositions beingmerely exemplary.

Accordingly, referring now to FIGS. 5 a-5 c , various embodiments of thedistributed (CUe/DUe) gNB architecture according to the presentdisclosure are described. As shown in FIG. 5 a , a first architecture520 includes a gNB 522 having an enhanced CU (CUe) 524 and a pluralityof enhanced DUs (DUe) 526. As described in greater detail subsequentlyherein, these enhanced entities are enabled to permit inter-processsignaling and high data rate, low latency services, whether autonomouslyor under control of another logical entity (such as the NG Core 523 withwhich the gNB communicates, or components thereof), as well as unifiedmobility and IoT services.

The individual DUe's 526 in FIG. 5 a communicate data and messaging withthe CUe 524 via interposed physical communication interfaces 528 andlogical interfaces 410. As previously described, such interfaces mayinclude a user plane and control plane, and be embodied in prescribedprotocols such as F1AP. Operation of each DUe and CUe are described ingreater detail subsequently herein; however, it will be noted that inthis embodiment, one CUe 524 is associated with one or more DUe's 526,yet a given DUe is only associated with a single CUe. Likewise, thesingle CUe 524 is communicative with a single NG Core 523, such as thatoperated by an MSO. Each NG Core 523 may have multiple gNBs 522associated therewith (e.g., of the type 504 shown in FIG. 5 ).

In the architecture 540 of FIG. 5 b , two or more gNBs 522 a-n arecommunicative with one another via e.g., an Xn interface 527, andaccordingly can conduct at least CUe to CUe data transfer andcommunication. Separate NG Cores 523 a-n are used for control and userplane (and other) functions of the network.

In the architecture 560 of FIG. 5 c , two or more gNBs 522 a-n arecommunicative with one another via e.g., the Xn interface 527, andaccordingly can conduct at least CUe to CUe data transfer andcommunication. Moreover, the separate NG Cores 523 a-n are logically“cross-connected” to the gNBs 522 of one or more other NG Cores, suchthat one core can utilize/control the infrastructure of another, andvice versa. This may be in “daisy chain” fashion (i.e., one gNB iscommunicative one other NG Core other than its own, and that NG Core iscommunicate with yet one additional gNB 522 other than its own, and soforth), or the gNBs 522 and NG Cores 523 may form a “mesh” topologywhere multiple Cores 523 are in communication with multiple gNBs ormultiple different entities (e.g., service providers). Yet othertopologies will be recognized by those of ordinary skill given thepresent disclosure. This cross-connection approach advantageously allowsfor, inter alia, sharing of infrastructure between two MSOs, or betweenMNO and MSO, which is especially useful in e.g., dense deploymentenvironments which may not be able to support multiple sets of RANinfrastructure, such as for different service providers.

It will also be appreciated that while described primarily with respectto a unitary gNB-CUe entity or device 504, 524 as shown in FIGS. 5-5 c,the present disclosure is in no way limited to such architectures. Forexample, the techniques described herein may be implemented as part of adistributed or dis-aggregated or distributed CUe entity (e.g., onewherein the user plane and control plane functions of the CUe aredis-aggregated or distributed across two or more entities such as aCUe-C (control) and CUe-U (user)), and/or other functional divisions areemployed.

It is also noted that heterogeneous architectures of eNBs or femtocells(i.e., E-UTRAN LTE/LTE-A Node B's or base stations) and gNBs may beutilized consistent with the architectures of FIGS. 5-5 c. For instance,a given DUe may (in addition to supporting node operations as discussedin greater detail with respect to FIGS. 7-7 a below), act (i) solely asa DUe (i.e., 5G NR PHY node) and operate outside of an E-UTRANmacrocell, or (ii) be physically co-located with an eNB or femtocell andprovide NR coverage within a portion of the eNB macrocell coverage area,or (iii) be physically non-colocated with the eNB or femtocell, butstill provide NR coverage within the macrocell coverage area.

In accordance with the 5G NR model, the DUe(s) 526 comprise logicalnodes that each may include varying subsets of the gNB functions,depending on the functional split option. DUe operation is controlled bythe CUe 524 (and ultimately for some functions by the NG Core 523).Split options between the DUe and CUe in the present disclosure mayinclude for example:

-   -   Option 1 (RRC/PCDP split)    -   Option 2 (PDCP/RLC split)    -   Option 3 (Intra RLC split)    -   Option 4 (RLC-MAC split)    -   Option 5 (Intra MAC split)    -   Option 6 (MAC-PHY split)    -   Option 7 (Intra PHY split)    -   Option 8 (PHY-RF split)

Under Option 1 (RRC/PDCP split), the RRC (radio resource control) is inthe CUe 524 while PDCP (packet data convergence protocol), RLC (radiolink control), MAC, physical layer (PHY) and RF are kept in the DUe,thereby maintaining the entire user plane in the distributed unit.

Under Option 2 (PDCP/RLC split), there are two possible variants: (i)RRC, PDCP maintained in the CUe, while RLC, MAC, physical layer and RFare in the DU(s) 526; and (ii) RRC, PDCP in the CUe (with split userplane and control plane stacks), and RLC, MAC, physical layer and RF inthe DUe's 526.

Under Option 3 (Intra RLC Split), two splits are possible: (i) splitbased on ARQ; and (ii) split based on TX RLC and RX RLC.

Under Option 4 (RLC-MAC split), RRC, PDCP, and RLC are maintained in theCUe 524, while MAC, physical layer, and RF are maintained in the DUe's.

Under Option 5 (Intra-MAC split), RF, physical layer and lower part ofthe MAC layer (Low-MAC) are in the DUe's 526, while the higher part ofthe MAC layer (High-MAC), RLC and PDCP are in the CUe 524.

Under Option 6 (MAC-PHY split), the MAC and upper layers are in the CUe,while the PHY layer and RF are in the DUe's 526. The interface betweenthe CUe and DUe's carries data, configuration, and scheduling-relatedinformation (e.g. Modulation and Coding Scheme or MCS, layer mapping,beamforming and antenna configuration, radio and resource blockallocation, etc.) as well as measurements.

Under Option 7 (Intra-PHY split), different sub-options for UL (uplink)and DL downlink) may occur independently. For example, in the UL, FFT(Fast Fourier Transform) and CP removal may reside in the DUe's 526,while remaining functions reside in the CUe 524. In the DL, iFFT and CPaddition may reside in the DUe 526, while the remainder of the PHYresides in the CUe 524.

Finally, under Option 8 (PHY-RF split), the RF and the PHY layer may beseparated to, inter alia, permit the centralization of processes at allprotocol layer levels, resulting in a high degree of coordination of theRAN. This allows optimized support of functions such as CoMP, MIMO, loadbalancing, and mobility.

Generally speaking, the foregoing split options are intended to enableflexible hardware implementations which allow scalable cost-effectivesolutions, as well as coordination for e.g., performance features, loadmanagement, and real-time performance optimization. Moreoverconfigurable functional splits enable dynamic adaptation to various usecases and operational scenarios. Factors considered in determininghow/when to implement such options can include: (i) QoS requirements foroffered services (e.g. low latency to support 5G RAN requirements, highthroughput); (ii) support of requirements for user density and loaddemand per given geographical area (which may affect RAN coordination);(iii) availability of transport and backhaul networks with differentperformance levels; (iv) application type (e.g. real-time or non-realtime); (v) feature requirements at the Radio Network level (e.g. CarrierAggregation).

It is also noted that the “DU” functionality referenced in the varioussplit options above can itself be split across the DUe and itsdownstream components, such as the RF stages of the node 509 (see FIGS.7 and 7 a) and/or the CPEe 513. As such, the present disclosurecontemplates embodiments where some of the functionality typically foundwithin the DUe may be distributed to the node/CPEe.

It will further be recognized that user-plane data/traffic may also berouted and delivered apart from the CUe. In one implementation(described above), the CUe hosts both the RRC (control-plane) and PDCP(user-plane); however, as but one alternate embodiment, a so-called“dis-aggregated” CUe may be utilized, wherein a CUe-CP entity (i.e.,CUe—control plane) hosts only the RRC related functions, and a CUe-UP(CUe—user plane) which is configured to host only PDCP/SDAP (user-plane)functions.

The CUe-CP and CUe-UP entities can, in one variant, interface data andinter-process communications via an E1 data interface, although otherapproaches for communication may be used.

It will also be appreciated that the CUe-CP and CUe-UP may be controlledand/or operated by different entities, such as where one serviceprovider or network operator maintains cognizance/control over theCUe-UP, and another over the CUe-CP, and the operations of the twocoordinated according to one or more prescribed operational or servicepolicies or rules.

Referring again to FIG. 5 , the exemplary embodiment of the DUe 509 is astrand-mounted or buried DUe (along with the downstream radio chain(s),the latter which may include one or more partial or complete RRH's(remote radio heads) which include at least portions of the PHYfunctionality of the node (e.g., analog front end, DAC/ADCs, etc.). Ascan be appreciated, the location and configuration of each DUe/node maybe altered to suit operational requirements such as population density,available electrical power service (e.g., in rural areas), presence ofother closely located or co-located radio equipment, geographicfeatures, etc.

As discussed with respect to FIGS. 7-7 a below, the nodes 509 in theembodiment of FIG. 5 include multiple OFDM-based transmitter-receiverchains of 800 MHz nominal bandwidth, although this configuration ismerely exemplary. In operation, the node generates waveforms that aretransmitted in the allocated band (e.g., up to approximately 1.6 GHz),but it will be appreciated that if desired, the OFDM signals may ineffect be operated in parallel with signals carried in the below-800 MHzband, such as for normal cable system operations.

As shown in FIG. 5 , in one implementation, each node (and hence DUe) isin communication with its serving CUe via an F1 interface, and may beeither co-located or not co-located with the CUe. For example, anode/DUe may be positioned within the MSO HFC infrastructure proximate adistribution node within the extant HFC topology, such as before theN-way tap point 512, such that a plurality of premises (e.g., the shownresidential customers) can be served by the node/DUe via theaforementioned OFDM waveforms and extant HFC plant. In certainembodiments, each node/DUe 509, 526 is located closer to the edge of thenetwork, so as to service one or more venues or residences (e.g., abuilding, room, or plaza for commercial, corporate, academic purposes,and/or any other space suitable for wireless access). For instance, inthe context of FIG. 5 , a node might even comprise a CPEe or externalaccess node (each discussed elsewhere herein). Each radio node 506 a isconfigured to provide wireless network coverage within its coverage orconnectivity range for its RAT (e.g., 4G and/or 5G NR). For example, avenue may have a wireless NR modem (radio node) installed within theentrance thereof for prospective customers to connect to, includingthose in the parking lot via inter alia, their NR or LTE-enabledvehicles or personal devices of operators thereof.

Notably, different classes of DUe/node 509, 526 may be utilized. Forinstance, a putative “Class A” LTE eNB may transmit up X dbm, while a“Class-B” LTE eNBs can transmit up to Y dbm (Y>X), so the average areacan vary widely. In practical terms, a Class-A device may have a workingrange on the order of hundreds of feet, while a Class B device mayoperate out to thousands of feet or more, the propagation and workingrange dictated by a number of factors, including the presence of RF orother interferers, physical topology of the venue/area, energy detectionor sensitivity of the receiver, etc. Similarly, different types ofNR-enabled nodes/DUe 509, 526 can be used depending on these factors,whether alone or with other wireless PHYs such as WLAN, etc.

Signal Attenuation and Bandwidth

FIGS. 6 a and 6 b illustrate exemplary downstream (DS) and upstream (US)data throughputs or rates as a function of distance within the HFC cableplant of FIG. 5 . As illustrated, a total (DS and US combined) bandwidthon the order of 10 Gbps is achievable (based on computerized simulationconducted by the Assignee hereof), at Node+2 at 2100 ft (640 m), and atNode+1 at 1475 ft (450 m). One exemplary split of the aforementioned 10Gbps is asymmetric; e.g., 8 Gbps DL/2 Gbps UL, although this may bedynamically varied using e.g., TDD variation as described elsewhereherein.

Notably, the portions of the extant HFC architecture described above(see e.g., FIGS. 1 and 2 ) utilized by the architecture 500 of FIG. 5are not inherently limited by their medium and architecture (i.e.,optical fiber transport ring, with coaxial cable toward the edges);coaxial cable can operate at frequencies significantly higher than thesub-1 GHz typically used in cable systems, but at a price ofsignificantly increased attenuation. As is known, the formula fortheoretical calculation of attenuation (A) in a typical coaxial cableincludes the attenuation due to conductors plus attenuation due to thedielectric medium:

A=4.35(R _(t) /Z ₀)+2√{square root over (E)}78 pF

-   -   =dB per 100 ft.        where:    -   R_(t)=Total line resistance ohms per 1000 ft.    -   R_(t)=0.1 (1/d+1√{square root over (F)}D) (for sing copper line)    -   p=Power factor of dielectic    -   F=Frequency in megahertz (MHz)

As such, attenuation increases with increasing frequency, and hencethere are practical restraints on the upper frequency limit of theoperating band. However, these restraints are not prohibitive in rangesup to for example 2 GHz, where with suitable cable and amplifiermanufacturing and design, such coaxial cables can suitably carry RFsignals without undue attenuation. Notably, a doubling of the roughly800 MHz-wide typical cable RF band (i.e., to 1.6 GHz width) is verypossible without suffering undue attenuation at the higher frequencies.

It will also be appreciated that the attenuation described above is afunction of, inter alia, coaxial conductor length, and hence higherlevels of “per-MHz” attenuation may be acceptable for shorter runs ofcable. Stated differently, nodes serviced by shorter runs of cable maybe able to better utilize the higher-end portions of the RF spectrum(e.g., on the high end of the aforementioned exemplary 1.6 GHz band) ascompared to those more distant, the latter requiring greater ordisproportionate amplification. As such, the present disclosurecontemplates use of selective mapping of frequency spectrum usage as afunction of total cable medium run length or similar.

Another factor of transmission medium performance is the velocity factor(VF), also known as wave propagation speed or velocity of propagation(VoP), defined as the ratio of the speed at which a wavefront (of anelectromagnetic or radio frequency signal, a light pulse in an opticalfiber or a change of the electrical voltage on a copper wire) propagatesover the transmission medium, to the speed of light (c, approximately3E08 m/s) in a vacuum. For optical signals, the velocity factor is thereciprocal of the refractive index. The speed of radio frequency signalsin a vacuum is the speed of light, and so the velocity factor of a radiowave in a vacuum is 1, or 100%. In electrical cables, the velocityfactor mainly depends on the material used for insulating thecurrent-carrying conductor(s). Velocity factor is an importantcharacteristic of communication media such as coaxial, CAT-5/6 cables,and optical fiber. Data cable and fiber typically has a VF betweenroughly 0.40 and 0.8 (40% to 80% of the speed of light in a vacuum).

Achievable round-trip latencies in LTE (UL/DL) are on the order of 2 ms(for “fast” UL access, which eliminates need for scheduling requests andindividual scheduling grants, thereby minimizing latency, and shorterTTI, per Release 15), while those for 5G NR are one the order of 1 ms orless, depending on transmission time interval frequency (e.g., 60 kHz).

Notably, a significant portion of 4G/4.5G transport latency relates tonetwork core and transport (i.e., non-edge) portions of the supportinginfrastructure.

Hence, assuming a nominal 0.7 VF and a one (1) ms roundtrip latencyrequirement, putative service distances on the order of 100 km arepossible, assuming no other processing or transport latency:

0.5E-03 s (assume symmetric US/DS)×(0.7×3E08 m/s)×1 km/1000 m=1.05E02 km

Network Node and DUe Apparatus—

FIGS. 7 and 7 a illustrate exemplary configurations of a network radiofrequency node apparatus 509 according to the present disclosure. Asreferenced above, these nodes 509 can take any number of form factors,including (i) co-located with other MSO equipment, such as in aphysically secured space of the MSO, (ii) “strand” or pole mounted,(iii) surface mounted, and (iv) buried, so as to inter alia, facilitatemost efficient integration with the extant HFC (and optical)infrastructure, as well as other 4G/5G components such as the CUe 504.

As shown, in FIG. 7 , the exemplary node 509 in one embodiment generallyincludes an optical interface 702 to the HFC network DWDM system (seeFIG. 2 ), as well as a “Southbound” RF interface 704 to the HFCdistribution network (i.e., coax). The optical interface 702communicates with an SFP connector cage 706 for receiving the DWDMsignals via the interposed optical fiber. A 5G NR DUe 506 is alsoincluded to provide 5G DU functionality as previously described, basedon the selected option split. The MIMO/radio unit (RU) stages 708operate at baseband, prior to upconversion of the transmitted waveformsby the IF (intermediate frequency) stages 710 as shown. As discussedbelow, multiple parallel stages are used in the exemplary embodiment tocapitalize on the multiple parallel data streams afforded by the MIMOtechnology within the 3GPP technology. A tilt stage 712 is also utilizedprior to the diplexer stage 714 and impedance matching stage 716.Specifically, in one implementation, this “tilt” stage is used tocompensate for non-linearity across different frequencies carried by themedium (e.g., coaxial cable). For instance, higher frequencies may havea higher loss per unit distance when travelling on the medium ascompared to lower frequencies travelling the same distance on the samemedium. When a high bandwidth signal (e.g. 50-1650 MHz) is transmittedon a coax line, its loss across the entire frequency bandwidth will notbe linear, and may include shape artifacts such as a slope (or “tilt”),and/or bends or “knees” in the attenuation curve (e.g., akin to alow-pass filter). Such non-linear losses may be compensated for toachieve optimal performance on the medium, by the use of one or moretilt compensation apparatus 712 on the RF stage of the node device.

A synchronization signal generator 718 is also used in some embodimentsas discussed in greater detail below with respect to FIG. 7 a.

In the exemplary implementation of FIG. 7 a , both 4G and 5G gNB DUe707, 506 are also included to support the RF chains for 4G and 5Gcommunication respectively. As described in greater detail below, the 5Gportion of the spectrum is divided into two bands (upper and lower),while the 4G portion is divided into upper and lower bands within adifferent frequency range. In the exemplary implementation, OFDMmodulation is applied to generate a plurality of carriers in the timedomain. See, e.g., co-owned and co-pending U.S. Pat. No. 9,185,341issued Nov. 10, 2015 and entitled “Digital domain content processing anddistribution apparatus and methods,” and U.S. Pat. No. 9,300,445 issuedMar. 29, 2016 also entitled “Digital domain content processing anddistribution apparatus and methods,” each incorporated herein byreference in their entirety, for inter alia, exemplary reprogrammableOFDM-based spectrum generation apparatus useful with various embodimentsof the node 509 described herein.

In the exemplary embodiment, the 5G and LTE OFDM carriers produced bythe node 509 utilize 1650 MHz of the available HFC bearer bandwidth, andthis bandwidth is partitioned into two or more sub-bands depending one.g., operational conditions, ratio of “N+0” subscribers served versus“N+i” subscribers served, and other parameters. In one variant, eachnode utilizes RF power from its upstream nodes to derive electricalpower, and further propagate the RF signal (whether at the same ofdifferent frequency) to downstream nodes and devices including thewideband amplifiers.

While the present embodiments are described primarily in the context ofan OFDM-based PHY (e.g., one using IFFT and FFT processes with multiplecarriers in the time domain) along with TDD (time division duplex)temporal multiplexing, it will be appreciated that other PHY/multipleaccess schemes may be utilized consistent with the various aspects ofthe present disclosure, including for example and without limitation FDD(frequency division duplexing), direct sequence or other spreadspectrum, and FDMA (e.g., SC-FDMA or NB FDMA).

As a brief aside, to achieve high throughput using a single receiverchipset in the consumer premises equipment (CPEe) 513 and 3GPP 5G NRwaveforms over a single coaxial feeder, such as the coaxial cable thatMSOs bring to their subscriber's premises or the single coaxial cablethat is installed for lower-cost single input single output (SISO)distributed antenna systems (DAS), the total carrier bandwidth that canbe aggregated by the chipset is limited to a value, e.g. 800 MHz, whichis insufficient for reaching high throughputs such as 10 Gbit/s usingone data stream alone given the spectral efficiencies supported by the3GPP 5G NR standard.

Since the 3GPP 5G NR standard supports the transmission of multipleindependent parallel data streams as part of a multiple input multipleoutput (MIMO) channel for the same RF bandwidth to leverage the spatialdiversity that wireless channels afford when multiple antenna elementsare used, the very first generation of 3GPP 5G chipsets will supportsuch parallel MIMO data streams. However, attempts to transmit theseparallel streams over a single cable would generally becounterproductive, as all the streams would occupy the same RF bandwidthand would interfere with each other for lack of spatial diversitybetween them.

Accordingly, the various embodiments disclosed herein (FIGS. 7 and 7 a)leverage the parallel MIMO data streams supported by 3GPP 5G NR, whichare shifted in frequency in a transceiver node before being injectedinto the single coaxial feeder so that frequency diversity (instead ofspatial diversity; spatial diversity may be utilized at the CPEe and/orsupplemental pole-mounted radio access node if desired) is leveraged toachieve the maximum total carrier bandwidth that 3GPP 5G NR chipsetswill support with parallel data streams.

Also, since higher frequencies attenuate much more over the coaxialtransmission media than lower frequencies, in one variant theIntermediate Frequencies (IF) are transmitted over the media, andblock-conversion to RF carrier frequency is employed subsequently in theconsumer premises equipment (CPEe) 513 for 3GPP band-compliantinteroperability with the 3GPP 5G NR chipset in the CPEe. In thisfashion, attenuation that would otherwise be experienced by conversionearlier in the topology is advantageously avoided.

The IF carriers injected by the transceiver node into the coaxial feeder704 can be received by multiple CPEe 513 that share the feeder as acommon bus using directional couplers and power dividers or taps.Point-to-Multipoint (PtMP) downstream transmissions from the node 509 tothe CPEe 513 can be achieved by, for instance, scheduling payload fordifferent CPEe on different 3GPP 5G NR physical resource blocks (PRB)which are separated in frequency.

In the exemplary embodiment, the vast majority of bandwidth in thecoaxial cable bearer is used in Time Division Duplex (TDD) fashion toswitch between downstream (DS) and upstream (US) 5G NR communications.Upstream communications from the multiple CPEe 513 to the transceivernode can also/alternatively occur simultaneously over separate PRBs(frequency separation).

In one variant (see FIG. 7 a ), a minor portion of the lower spectrum(since lower frequencies attenuate less on the cable) is allocated to a3GPP 4G LTE MIMO carrier with up to two parallel streams of 20 MHzbandwidth for a total of 40 MHz. This is performed since 3GPP Release 15only supports 5G NR in Non-Standalone (NSA) mode, whereby it mustoperate in tandem with a 4G LTE carrier. Just as with the parallel 5Gstreams, the two parallel LTE MIMO streams are to be offset in frequencyso as to not interfere with each other and are configured in theexemplary embodiment to operate in TDD mode.

As an aside, 5G NR supports adaptive TDD duty cycles, whereby theproportion of time allocated for downstream and upstream transmissionscan be adapted to the net demand for traffic from the total set oftransmitting network elements, viz. the node and all the CPEe 513sharing the coaxial bus with the node. 4G LTE does not support suchadaptive duty cycles. To prevent receiver blocking in the likelyscenario that the 5G and 4G duty cycles differ, high-rejection filtercombiners 714 are used in all active network elements, viz. transceivernodes, inline amplifiers and CPEe 513 for the 4G and 5G carriers to notinterfere with each other or cause receiver blocking. In the exemplarydiplexer of FIG. 7 a , both 4G and 5G are addressed via a high-rejectionfilter to allow for different duty cycles.

In one variant, another minor portion of the lower spectrum on thecoaxial cable employs one-way communication in the downstream for thetransmission of two digital synchronization channels, one for 5G and onefor 4G, which are I-Q multiplexed onto one QPSK analog synchronizationchannel within the aforementioned “minor portion” from the signalgenerator 718 of the transceiver node 509 to the multiple inlineamplifiers and CPEe 513 that may be sharing the coaxial bus. Thesesynchronization channels aid coherent reception of the PRBs, and in onevariant command the network elements to switch between downstream andupstream communication modes according to the TDD duty cycle set by thetransceiver node 509. In the exemplary configuration, two digitalsynchronization channels are required since the 5G and 4G streams mayhave different upstream-downstream ratios or duty-cycles. Since lowerfrequencies attenuate less on the cable, the synchronization channel isin one implementation transmitted over a lower portion of the spectrumon the cable so that it reaches every downstream network element andCPEe. In one variant, an analog signal is modulated with two bits, whereone bit switches according to the duty cycle for the 4G signal, and theother bit switches according to the duty cycle of the 5G signal,although other approaches may be utilized.

The connectivity between the transceiver node 509 and the northboundnetwork element is achieved with a fiber optic link 702 to the MSO DWDMplant. To minimize the number of fiber channels required to feed thetransceiver node 509, and to restrict it to a pair of fiber strands, inone embodiment the 3GPP 5G NR F1 interface (described supra) is realizedover the fiber pair to leverage the low overhead of the F1 interface.The 3GPP 5G NR Distribution Unit (DUe) functionality is incorporatedinto the transceiver node 509 as previously described, since the F1interface is defined between the Central Unit (CU/CUe) and DU/DUe where,in the illustrated embodiment, the CUe and DUe together constitute a3GPP 5G NR base station or gNB (see FIGS. 5 a-5 c ).

An Ethernet switch 705 is also provided at the optical interface in theembodiment of FIG. 7 a to divide the backhaul into the 4G and 5G datapaths (e.g., the received upstream 4G and 5G signals are respectivelyrouted differently based on the switch 705).

The exemplary node 509 also includes a power converter 719 to adapt forinternal use of quasi-square wave low voltage power supply technologyover HFC used by DOCSIS network elements as of the date of thisdisclosure. The node 509 in one variant is further configured to passthe quasi-square wave low voltage power received on the input port 701through to the HFC output port 704 to other active network elements suchas e.g., amplifiers, which may be installed downstream of the node onthe HFC infrastructure.

It is noted that as compared to some extant solutions, the illustratedembodiment of FIGS. 5 and 7-7 a uses HFC versus twisted pair to feed theCPEe 513; HFC advantageously provides lower loss and wider bandwidthsthan twisted pair, which is exploited to provide 5G throughputs tofarther distances, and to leverage the large existing base of installedcoaxial cable. Moreover, the foregoing architecture in oneimplementation is configured to serve multiple CPEe 513 usingdirectional couplers and power dividers or taps to attach to a commoncoaxial bus which connects to a single interface at the transceivernode. The aforementioned Ethernet services (necessary to service anexternal Wi-Fi access-point and an integrated Wi-Fi router) are furtheradded in other implementations to provide expanded capability, incontrast to the existing solutions.

CPEe Apparatus—

FIG. 8 illustrates an exemplary configuration of a CPEe apparatus 513according to the present disclosure. As shown, the CPEe 513 generally anRF input interface 816 to the HFC distribution network (i.e., coax dropat the premises). A transmitter/receiver architecture generallysymmetrical to the transmitter/receiver of the node 509 discussedpreviously is used; i.e., impedance matching circuitry, diplexer,synchronization circuit, tilt, etc. are used as part of the CPEe RFfront end. Block converters 810 are used to convert to and from thecoaxial cable domain bands (here, 50-850 and 850-1650 MHz) to thepremises domain, discussed in greater detail below.

The exemplary CPEe 513 also includes a 5G UE process 808 to implement3GPP functionality of the UE within the CPEe, and 3GPP (e.g., 5G/LTE)repeater module 809 which includes one or more antennae elements 810 forindoor/premises coverage within the user RF band(s). As such, the CPEe513 shown can in effect function as a base station for user deviceswithin the premises operating within the user band(s).

A 10 GbE WLAN port 818 is also included, which interfaces between the UEmodule 808 and the (optional) WLAN router 517 with internal 10 GbEswitch 819) to support data interchange with premises WLANinfrastructure such as a Wi-Fi AP.

Also shown in the configuration of FIG. 8 are several external ports812, 814 for external antenna 516 connection (e.g., roof-top antennaelement(s) used for provision of the supplemental data link aspreviously described with respect to FIG. 5 ), wireless high-bandwidthbackhaul, or other functions.

In the exemplary implementation of FIG. 8 a , both 4G and 5G gNB blockconverters 832, 830 are included to support the RF chains for 4G and 5Gcommunication respectively (i.e., for conversion of the IF-band signalsreceived to the relevant RF frequencies of the 4G/5G interfaces andmodems within the CPEe, such as in the 2 GHz band. The block convertersalso enable upstream communication with the distribution node 509 viathe relevant IF bands via the coaxial input 816 as previously described.

Notably, the CPEe 513 applies block-conversion between the IF and RFcarrier frequency for the 4G and 5G carrier separately since they may beon different frequency bands. The CPEe includes in one implementation a5G NR and 4G LTE-capable user equipment (UE) chipset 816. The twotechnologies are supported in this embodiment, since the first releaseof 3GPP 5G NR requires 4G and 5G to operate in tandem as part of thenon-standalone (NSA) configuration.

It is noted that in the exemplary configuration of FIG. 8 a (showing thelower frequencies in 4G combined with 5G), a filter combiner is used (incontrast to the more generalized approach of FIG. 8 ).

It is also noted that the specific implementation of FIG. 8 a utilizes“tilt” compensation as previously described on only one of the RF-IFblock converters 830. This is due to the fact that the need for suchcompensation arises, in certain cases such as coaxial cable operated inthe frequency band noted) disproportionately at the higher frequencies(i.e., up to 1650 MHz in this embodiment). It will be appreciatedhowever that depending on the particular application, differentcompensation configurations may be used consistent with the presentdisclosure. For example, in one variant, the upper-band block converters830 may be allocated against more granular frequency bands, and hencetilt/compensation applied only in narrow regions of the utilizedfrequency band (e.g., on one or two of four % G RF-IF block converters).Similarly, different types of tilt/compensation may be applied to eachblock converter (or a subset thereof) in heterogeneous fashion. Variousdifferent combinations of the foregoing will also be appreciated bythose of ordinary skill given the present disclosure.

Block conversion to the RF frequency makes the signals 3GPPband-compliant and interoperable with the UE chipset in the CPEe 513.The RF carriers are also then amenable for amplification through theincluded repeater 809 for 4G and 5G which can radiate the RF carriers,typically indoors, through detachable external antennas 810 connected tothe CPEe. Mobile devices such as smartphones, tablets with cellularmodems and IoT devices can then serve off of the radiated signal for 4Gand 5G service (see discussion of FIGS. 9 a and 9 b below).

The UE chipset 816 and the repeater 809 receive separate digital I/Qsynchronization signals, one for 4G and one for 5G, for switchingbetween the downstream and upstream modes of the respective TDDcarriers, since they are likely to have different downstream-to-upstreamratios or duty cycle. These two digital synchronization signals arereceived from an I-Q modulated analog QPSK signal received fromlower-end spectrum on the coaxial cable that feeds the CPEe 513 via theport 816.

As noted, in the exemplary implementation, OFDM modulation is applied togenerate a plurality of carriers in the time domain at the distributionnode 509; accordingly, demodulation (via inter alia, FFT) is used in theCPEe to demodulate the IF signals. See, e.g., co-owned and co-pendingU.S. Pat. No. 9,185,341 issued Nov. 10, 2015 and entitled “Digitaldomain content processing and distribution apparatus and methods,” andU.S. Pat. No. 9,300,445 issued Mar. 29, 2016 also entitled “Digitaldomain content processing and distribution apparatus and methods,” eachincorporated herein by reference in their entirety, for inter alia,exemplary reprogrammable OFDM-based receiver/demodulation apparatususeful with various embodiments of the CPEe 513 described herein.

Similar to the embodiment of FIG. 8 , a 10 Gbe Ethernet port is alsoprovided to support operation of the WLAN router 517 in the device ofFIG. 8 a , including for LAN use within the served premises.

Further, to boost the broadband capacity beyond the capacity availablethrough the primary coaxial cable link and to add a redundant connectionfor higher reliability (which could be important for small businesses,enterprises, educational institutions, etc.), two additional RFinterfaces on the CPEe of FIG. 8 a are included for connecting the CPEeto a 2-port external antenna 516 which is installed outdoors, e.g., onthe roof of the small business, multi-dwelling unit (MDU) or multi-storyenterprise (see FIG. 9 a ). This external antenna can be used to receivesupplemental signals from outdoor radios installed in the vicinity ofthe consumer premises. It will be appreciated that the outdoor radiosmay have a primary purpose of providing coverage for outdoor mobility,but signals from them can also/alternatively be used in a fixed-wirelessmanner to supplement the capacity from the primary coaxial link and toadd redundancy, as described elsewhere herein.

Supplemental Link and Mobility Enhancement—

In a further embodiment of the architecture 500, a supplemental orcomplementary data link 902 is utilized to provide additional datacapacity (and redundancy to the primary link in the event of anequipment or other failure), as shown in FIG. 9 a . In thisconfiguration, data rates on the order of 21 Gbps can be achieved basedon computer modeling by the Assignee hereof; e.g., 17 Gbps DS and 4 GbpsUS. The supplemental link in one variant includes a 5G NR wirelessinterface between a pole-mounted or other external radio access node 506a, and the premises transceiver (which in one embodiment includes theCPEe 513 with added antenna capability 516. As used in the presentcontext, the terms “pole-mounted” and “external” refer withoutlimitation to any mounting placement or location which can establish aconnection or data connectivity with e.g., the supplemental antenna 516(e.g., roof-top or outdoor antenna) of the CPEe. Such mounting may beoutdoor or within a large structure (e.g., a sports stadium, largebuilding complex, and may be only temporary or semi-permanent in someimplementations.

FIG. 9 b illustrates an exemplary embodiment of a network architecture920 according to the present disclosure, including use of a supplementallink 902 in support of “seamless” mobility of a mobile user device.

Advantageously, as shown in FIG. 9 b , the use of common waveforms andprotocols over HFC and wireless in exemplary embodiments of thearchitecture 500 allow the use of common network elements such ascentralized authentication, authorization, and accounting (AAA)functions, packet gateway and mobility controller (MME) and a commonbase station for indoor and outdoor areas within a service area,provided the base station is split into a central unit (CUe) anddistribution unit (DUe) as described elsewhere herein. It is expectedthat such a split base station architecture can be ported back to 3GPP4G/4.5G LTE/A as well.

As illustrated in FIG. 9 b , the commonality of network elementsadvantageously enables seamless mobility experience between indoor andoutdoor spaces of the served premises, in part because macronetwork-grade network elements with high signaling capacity and datathroughput capacity control both spaces. Mobility between these spacesby devices such as phones and IoT modems trigger the least amount ofsignaling toward “northbound” network elements because, in many cases,mobility is constrained between distribution units (DUe 506) connectedto a common Central Unit (CUe 504) as illustrated by the dashed lines inFIG. 9 b , and generally in FIG. 5 .

Moreover, as previously described, data throughput performance-triggeredmobility between 3GPP and Wi-Fi is provided using a centralized Wi-Ficontroller connected to a 3GPP mobility controller which services bothindoor and outdoor spaces and with Wi-Fi access points cooperating withthe Wi-Fi controller 515.

In another embodiment, one or more external (exterior) mobility nodedevices are utilized to provide outdoor mobility to users/subscribers,including in-vehicle use scenarios. As shown in FIG. 10 , the “combined”cell coverage is large due to the unified common architecture of thesystem; no MSO-to-MNO (or vice versa) handovers are required while thevehicle remains in the combined cell coverage area served by the MSO,whether under WLAN APs or the 4G/5G external access nodes (which in oneembodiment, may include the pole-mounted devices 506 a shown in FIG. 5 ,and/or other devices such as those co-located at cellular base stationsites). Specifically, by virtue of the common operator (e.g., MSO) andinfrastructure, multiple mobility access nodes can be combined to form asingle cell for both higher throughput (e.g., at the cell edge) andgreater coverage, thereby further reducing handovers.

In one variant, the mobility access nodes are ruggedized versions of theCPEe 513, having generally comparable capabilities. For instance, in oneimplementation, the external access nodes include both a backhaul (fiberor HFC) to the MSO network, as well as a supplemental link antenna suchthat the access node can communicate with the pole-mounted devices 506 afor additional capacity as needed.

In another implementation, the mobility access nodes use thepole-mounted devices as their backhaul (alone).

WLAN nodes may also be backhauled through the mobility access nodes,including with provision of QoS.

It will also be appreciated that the common MSO core and RANarchitecture shown allows for the MSO to selectively supplement coverageusing a pole-mounted or other configuration DUe. For example, where anew home or neighborhood is built, the MSO can simply add one or moresuch DUe devices at locations determined to provide the desired level ofcoverage; this is in contrast to MNO-based cellular coverage, whereininstallation of a new base station (i) can't be directly controlled bythe MSO or integrated with other MSO services, (ii) is much more laborand capital intensive.

Yet other combinations and modifications will be appreciated by those ofordinary skill given the present disclosure.

DAS (Distributed Antenna System) Architecture—

In another aspect of the disclosure, an architecture for providing highdata rate, low latency and high mobility unified coverage to e.g., largeindoor spaces such as office buildings, enterprises, universities, etc.is disclosed. As shown in FIG. 11 , one implementation of thisarchitecture utilizes the foregoing hub 505 and CUe node 501 (includingaccess node 509 and CUe 504, as shown in FIG. 5 ) to supply one or moreCPEe 513 within the enterprise, etc. via HFC infrastructure. The CPEeare then connected to e.g., an indoor (or indoor/outdoor) DAS 1102 whichprovides coverage within the structure as shown. The CPEe 513 may alsoutilize the supplemental antenna capability previously described tosupplement bandwidth provided to the structure/enterprise as well asindoor/outdoor mobility, such as via local pole-mounted access node with4G/5G capability.

Methods

Referring now to FIGS. 12-12 c, methods of operating the networkinfrastructure of, e.g., FIG. 5 herein are shown and described.

FIG. 12 is a logical flow diagram illustrating one embodiment of ageneralized method 1200 of utilizing an existing network (e.g., HFC) forhigh-bandwidth data communication. As shown, the method includes firstidentifying content (e.g., digitally rendered media or other data, etc.)to be transmitted to the recipient device or node (e.g., a requestingCPEe 513 or UE in communication therewith) per step 1202.

Next, per step 1204, the transmission node 509 generates waveforms“containing” the identified content data. As described below, in oneembodiment, this includes generation of OFDM waveforms and scheduling oftime-frequency resources to carry the content data (e.g., PRBs).

Per step 1206, the waveforms are transmitted via the networkinfrastructure (e.g., coaxial cable and/or DWDM optical medium) to oneor more recipient nodes. It will be appreciated that such transmissionmay include relay or transmission via one or more intermediary nodes,including for instance one or more N-way taps (FIG. 5 ), optical nodes,repeaters, etc.).

Per step 1208, the transmitted waveforms are received at the recipientnode (e.g., CPEe 513 in one instance).

The waveforms are then upconverted in frequency (e.g., to the specifieduser frequency band per step 1212, and transmitted per step 1214 via thelocal (e.g., premises RAN or distribution medium) for use by, e.g.,consuming or requesting UE.

FIG. 12 a is a logical flow diagram illustrating one particularimplementation of content processing and transmission methods 1220according to the generalized method of FIG. 12 . Specifically, as shown,the method 1220 includes first performing a serial-to-parallelconversion of the content data per step 1222. Next, the parallelizeddata is mapped to its resources (step 1224), and an IFFT or other suchtransformation operation performed to convert the frequency-domainsignals to the time domain (step 1226). The transformed (time domain)data is then re-serialized (step 1228) and converted to the analogdomain (step 1230) for transmission over e.g., the RF interface such asa coaxial cable plant. In the exemplary embodiment, an upper band on theplant (e.g., 850-1650 MHz) is used, although it will be appreciated thatother frequency bands (and in fact multiple different frequency bands invarious portions of the spectrum) may be used for this purpose.

FIG. 12 b is a logical flow diagram illustrating one particularimplementation of content reception and digital processing methods 1240by a CPEe according to the generalized method of FIG. 12 . In thismethod 1240, the CPEe 513 receives the transmitted waveforms (see step1232 of the method 1220), and performs analog-domain upconversion to thetarget frequency (e.g., user band) per step 1242.

Per step 1244, the upconverted signals are synchronized via therecovered UQ signals via the synchronization circuit of the CPEe, andthe upconverted signals are converted to the digital domain for use by,e.g., the chipset 816 of the CPEe 513 (see FIG. 8 a ). Within thechipset, the digital domain signals are processed including inter aliaserial-to-parallel conversion, FFT transformation of the data back tothe frequency domain (step 1250), de-mapping of the physical resources(step 1252), parallel-to-serial conversion (step 1254), and ultimatelydistribution of the digital (baseband) data to e.g., the 10 GbE switch,Wi-Fi router, etc. (step 1256).

FIG. 12 c is a logical flow diagram illustrating one particularimplementation of content reception and transmission within a premisesby a CPEe according to the generalized method of FIG. 12 . Specifically,as shown in FIG. 12 c , the method 1260 includes upconversion to theuser band (step 1262) as in the method 1240 described above, but ratherthan conversion to the digital domain as in the method 1240, theupconverted analog domain signals are synchronized (step 1264) andprovided to one or more repeater ports for transmission of theupconverted waveforms via the antenna(e) of the repeater module (seeFIG. 8 a ).

In exemplary implementations, supplemental link addition may beconducted according to any number of schemes, including withoutlimitation: (i) 3GPP-based CA (carrier aggregation), or (ii) use of anadditional MIMO (spatial diversity) layer.

It will be recognized that while certain aspects of the disclosure aredescribed in terms of a specific sequence of steps of a method, thesedescriptions are only illustrative of the broader methods of thedisclosure, and may be modified as required by the particularapplication. Certain steps may be rendered unnecessary or optional undercertain circumstances. Additionally, certain steps or functionality maybe added to the disclosed embodiments, or the order of performance oftwo or more steps permuted. All such variations are considered to beencompassed within the disclosure disclosed and claimed herein.

While the above detailed description has shown, described, and pointedout novel features of the disclosure as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the disclosure. Thisdescription is in no way meant to be limiting, but rather should betaken as illustrative of the general principles of the disclosure. Thescope of the disclosure should be determined with reference to theclaims.

It will be further appreciated that while certain steps and aspects ofthe various methods and apparatus described herein may be performed by ahuman being, the disclosed aspects and individual methods and apparatusare generally computerized/computer-implemented. Computerized apparatusand methods are necessary to fully implement these aspects for anynumber of reasons including, without limitation, commercial viability,practicality, and even feasibility (i.e., certain steps/processes simplycannot be performed by a human being in any viable fashion).

1.-21. (canceled)
 22. A network architecture configured to supportwireless user devices, the network architecture comprising: adistribution node, the distribution node configured to transmit radiofrequency (RF) waveforms onto a wireline or optical medium of a network,the RF waveforms being orthogonal frequency division multiplex (OFDM)modulated; and a first plurality of user nodes, each of the firstplurality of user nodes in data communication with the wireline oroptical medium and comprising a receiver apparatus configured to:receive the transmitted OFDM modulated waveforms; upconvert the receivedOFDM modulated waveforms to at least one user frequency band to formupconverted waveforms; and transmit the upconverted waveforms to atleast one wireless user device.
 23. The network architecture of claim22, further comprising a radio node in data communication with thedistribution node and at least one of the first plurality of user nodes,the radio node configured to provide at least supplemental datacommunication to at least one of the first plurality of user nodes. 24.The network architecture of claim 23, wherein the radio node is in datacommunication with the distribution node via at least an optical fibermedium, and the radio node is in data communication with at least one ofthe first plurality of user nodes via a wireless interface.
 25. Thenetwork architecture of claim 22, wherein the receipt of the transmittedOFDM modulated waveforms comprises utilization of TDD (time divisionduplex) multiplexing.
 26. The network architecture of claim 22, furthercomprising a second distribution node, the second distribution nodeconfigured to transmit radio frequency (RF) waveforms onto a secondwireline or optical medium of the network, the RF waveforms beingorthogonal frequency division multiplex (OFDM) modulated, the secondwireline or optical medium of the network serving a second plurality ofuser nodes different than the first plurality of user nodes.
 27. Thenetwork architecture of claim 26, further comprising a radio node indata communication with at least the distribution node and (i) at leastone of the first plurality of user nodes, and (ii) at least one of thesecond plurality of user nodes, the radio node configured to provide atleast supplemental data communication to both the at least one of thefirst plurality of user nodes, and the at least one of the secondplurality of user nodes; wherein the radio node is in data communicationwith the distribution node via at least an optical fiber medium, and theradio node is in data communication with both the at least one of thefirst plurality of user nodes, and the at least one of the secondplurality of user nodes, via a wireless interface utilizing anunlicensed portion of sn RF spectrum.
 28. The network architecture ofclaim 22, further comprising at least one wireless local area node, theat least one wireless local area node in data communication with atleast one of the first plurality of user nodes, the at least onewireless local area node configured to wirelessly communicate with theat least one wireless user device via unlicensed radio frequencyspectrum not within the at least one user frequency band.
 29. Thenetwork architecture of claim 28, further comprising at least onewireless local area node controller in data communication with thedistribution node, the at least one wireless local area node controllerconfigured to cooperate with the distribution node to effect handover ofone or more wireless sessions between the at least one wireless localarea node and the at least one of the first plurality of user nodes. 30.The network architecture of claim 29, wherein the at least one wirelesslocal area node operates within a first unlicensed frequency band, andthe at least one of the first plurality of user nodes operates within asecond unlicensed frequency band.
 31. The network architecture of claim30, wherein the at least one wireless local area node operates accordingto an IEEE-Std. 802.11 (Wi-Fi) protocol, and the at least one of thefirst plurality of user nodes operates according a 3GPP 5G NR (FifthGeneration, New Radio) protocol.
 32. Controller apparatus for use withina hybrid fiber/coaxial cable distribution network, the controllerapparatus comprising: a radio frequency (RF) communications managementmodule; a first data interface in data communication with the RFcommunications management module for data communication with a networkcore process; a second data interface in data communication with the RFcommunications management module for data communication with a first RFdistribution node of the hybrid fiber/coaxial cable distributionnetwork; and a third data interface in data communication with the RFcommunications management module for data communication with a second RFdistribution node of the hybrid fiber/coaxial cable distributionnetwork; wherein the radio frequency (RF) communications managementmodule comprises computerized logic to enable at least transmission ofdigital data from at least one of the first RF distribution node and thesecond RF distribution node with an RF band outside of that normallyused by the first RF distribution node and the second RF distributionnode.
 33. The controller apparatus of claim 32, wherein: the RFcommunications management module comprises a 3GPP Fifth Generation NewRadio (5G NR) gNB (gNodeB) Controller Unit (CU); the first datainterface for data communication with the network core process comprisesa 3GPP Fifth Generation New Radio (5G NR) Xn interface with a 5GC (FifthGeneration Core); the second data interface comprises a 3GPP FifthGeneration New Radio (5G NR) F1 interface operative over at least awireline data bearer medium, the first RF distribution node comprising a3GPP Fifth Generation New Radio (5G NR) gNB (gNodeB) Distributed Unit(DU); and the third data interface comprises an Fifth Generation NewRadio (5G NR) F1 interface operative over at least a dense wave divisionmultiplexed (DWDM) optical data bearer, the second RF distribution nodecomprising a 3GPP Fifth Generation New Radio (5G NR) gNB (gNodeB)Distributed Unit (DU).
 34. A computerized method of operating a radiofrequency (RF) network so that extant infrastructure is used for receiptof integrated wireless data services, the computerized methodcomprising: receiving, from a distribution node and at a receiverapparatus of a user node, OFDM (orthogonal frequency divisionmultiplexing) waveforms over at least a portion of the extantinfrastructure using at least a frequency band wider in frequency than anormal operating band of the extant infrastructure, the frequency bandbeing lower in frequency than a user frequency band; upconverting theOFDM waveforms to the user frequency band to form upconverted waveforms;and causing transmission of the upconverted OFDM waveforms to at leastone computerized user device.
 35. The computerized method of claim 34,wherein: the extant infrastructure comprises a hybrid fiber coax (HFC)infrastructure; the integrated wireless data services comprise datadelivery at rates in excess of 1 Gbps; and the receiving of the OFDMwaveforms comprises receiving the OFDM waveforms via at least coaxialcable infrastructure of the HFC infrastructure.
 36. The computerizedmethod of claim 34, wherein the frequency band wider in frequency thanthe normal operating band of the extant infrastructure comprises afrequency band of at least 1.6 GHz in total bandwidth.
 37. Thecomputerized method of claim 34, wherein the upconverting the receivedOFDM waveforms to the user frequency band comprises upconverting to afrequency band including 5 GHz.
 38. The computerized method of claim 34,wherein the causing of the transmission of the upconverted OFDMwaveforms to the at least one computerized user device comprisestransmitting using at least a 3rd Generation Partnership Project (3GPP)Fifth Generation (5G) New Radio (NR) compliant air interface in anunlicensed radio frequency band.
 39. The computerized method of claim34, wherein the receiving of the OFDM waveforms comprises receiving theOFDM waveforms over at least coaxial cable and via a plurality ofamplifier stages associated with the coaxial cable.
 40. The computerizedmethod of claim 34, further comprising converting the upconverted OFDMwaveforms to digital baseband data.
 41. The computerized method of claim34, wherein: the upconverted OFDM waveforms are in an analog domain; andthe causing of the transmission of the upconverted OFDM waveforms to theat least one computerized user device comprises transmitting theupconverted OFDM waveforms in the analog domain to one or more repeaterports for transmission of the upconverted OFDM waveforms via one or moreantennae of a repeater module.